All Activity

This stream auto-updates   

  1. Past hour
  2. I ran into an issue that someone else might have as well. I cannot close the server. It fails at shutting down the db core. I'm using FreeBSD 11 32 Bit and I've compiled the source. TL;DR: Running the server works but shutting down fails with db core (100% CPU usage).
  3. Hello,What i do ? In DB config MIN_LENGTH_OF_SOCIAL_ID = 6 to MIN_LENGTH_OF_SOCIAL_ID = 7 SIMPLE_SOCIALID = 0 to SIMPLE_SOCIALID = 1 TABLE_POSTFIX = " " to TABLE_POSTFIX = "" PLAYER_DELETE_CHECK_SIMPLE = 0 to PLAYER_DELETE_CHECK_SIMPLE = 1
  4. Items is disappearing after reboot I think the problem in query but how to fix?? I tried to reinstall mysql but no thing how to solve it?
  5. Hey guys, ich have a compile error by compiling my client binary: whats my error? Need help please... greets..
  6. Today
  7. -

    -Solved.
  8. First, All port is openned ? Second, Server port and client port correct? My test. i checked,i not have error or something. I just have clear syslog and 0 syserr Old time i getted this error : Bad modifyded root or uiscript ...
  9. I have done all this, it is not constant, or it is only sometimes that gives, but when I give no loga or with prayer, something I noticed different is these errors here SYSERR: Feb 20 13:55:34 :: Analyze: input_login: login phase does not handle this packet! header 3 SYSERR: Feb 20 13:56:52 :: Analyze: input_login: login phase does not handle this packet! header 8 SYSERR: Feb 20 13:57:59 :: Analyze: input_login: login phase does not handle this packet! header 2 SYSERR: Feb 20 14:02:06 :: Analyze: input_login: login phase does not handle this packet! header 18 SYSERR: Feb 20 14:02:54 :: Analyze: input_login: login phase does not handle this packet! header 12 SYSERR: Feb 20 14:03:19 :: Analyze: input_login: login phase does not handle this packet! header 13 SYSERR: Feb 20 14:06:11 :: Analyze: input_login: login phase does not handle this packet! header 20 SYSERR: Feb 20 14:08:32 :: Analyze: input_login: login phase does not handle this packet! header 28 SYSERR: Feb 20 14:10:35 :: Analyze: input_login: login phase does not handle this packet! header 29 SYSERR: Feb 20 14:19:05 :: Analyze: input_login: login phase does not handle this packet! header 50 SYSERR: Feb 20 14:21:00 :: Analyze: input_login: login phase does not handle this packet! header 54 SYSERR: Feb 20 14:22:38 :: Analyze: input_login: login phase does not handle this packet! header 53 SYSERR: Feb 20 14:22:38 :: Analyze: input_login: login phase does not handle this packet! header 78 SYSERR: Feb 20 14:23:37 :: Analyze: input_login: login phase does not handle this packet! header 51 SYSERR: Feb 20 14:23:37 :: Analyze: input_login: login phase does not handle this packet! header 52 SYSERR: Feb 20 14:23:57 :: Analyze: input_login: login phase does not handle this packet! header 66 SYSERR: Feb 20 14:24:04 :: Analyze: input_login: login phase does not handle this packet! header 69 SYSERR: Feb 20 14:24:08 :: Analyze: input_login: login phase does not handle this packet! header 70 SYSERR: Feb 20 14:24:44 :: Analyze: input_login: login phase does not handle this packet! header 71 SYSERR: Feb 20 14:25:13 :: Analyze: input_login: login phase does not handle this packet! header 65 SYSERR: Feb 20 14:26:24 :: Analyze: input_login: login phase does not handle this packet! header 74 SYSERR: Feb 20 14:29:23 :: Analyze: input_login: login phase does not handle this packet! header 69 SYSERR: Feb 20 14:32:00 :: Analyze: input_login: login phase does not handle this packet! header 80 SYSERR: Feb 20 14:32:20 :: Analyze: input_login: login phase does not handle this packet! header 82 SYSERR: Feb 20 14:32:20 :: CharacterSelect: no account table SYSERR: Feb 20 14:34:59 :: Analyze: input_login: login phase does not handle this packet! header 69 SYSERR: Feb 20 14:34:59 :: Analyze: input_login: login phase does not handle this packet! header 80 SYSERR: Feb 20 14:36:15 :: Analyze: input_login: login phase does not handle this packet! header 83 SYSERR: Feb 20 15:51:36 :: Analyze: input_login: login phase does not handle this packet! header 206 SYSERR: Feb 20 16:32:52 :: Analyze: input_login: login phase does not handle this packet! header 3 SYSERR: Feb 20 16:35:01 :: Analyze: input_login: login phase does not handle this packet! header 8 SYSERR: Feb 20 16:35:18 :: Analyze: input_login: login phase does not handle this packet! header 2 SYSERR: Feb 20 16:40:32 :: Analyze: input_login: login phase does not handle this packet! header 15 SYSERR: Feb 20 16:43:05 :: Analyze: input_login: login phase does not handle this packet! header 18 SYSERR: Feb 20 16:45:17 :: Analyze: input_login: login phase does not handle this packet! header 26 SYSERR: Feb 20 16:45:50 :: Analyze: input_login: login phase does not handle this packet! header 28 SYSERR: Feb 20 16:48:16 :: Analyze: input_login: login phase does not handle this packet! header 70 SYSERR: Feb 20 16:56:49 :: Analyze: input_login: login phase does not handle this packet! header 50 SYSERR: Feb 20 16:59:49 :: Analyze: input_login: login phase does not handle this packet! header 255 SYSERR: Feb 20 17:03:09 :: Analyze: input_login: login phase does not handle this packet! header 53 SYSERR: Feb 20 17:08:45 :: Analyze: input_login: login phase does not handle this packet! header 69 SYSERR: Feb 20 17:10:14 :: Analyze: input_login: login phase does not handle this packet! header 73 SYSERR: Feb 20 17:10:33 :: Analyze: input_login: login phase does not handle this packet! header 72 SYSERR: Feb 20 17:11:42 :: Analyze: input_login: login phase does not handle this packet! header 78
  10. Hello,First connect u VPS or FreeBSD go to Auth + DB and check syslog and syserr extraxt Root.eix Root.epk game.py and check errors last modified file ? try restor back old file And quote u last work on client
  11. You should find character instance vector and filter by vnum range/type and live status.
  12. Is there a correlation and could someone help me correct this damn mistake? 0220 16:45:11258 :: 󸮵ÇÁö ¾ÊÀº ÆÐŶ Çì´õ 9, state Game 0220 16:45:11313 :: Unknown packet header: 35, last: 3 9
  13. same problem....
  14. Bump
  15. This is the problem. Put the map to CH99.
  16. Code it, I mean, just look inside devil's includes, then add it, a friend of mine did so, I can take a look if you want Edit : I may be wrong, you can use Direct3D instead, my bad
  17. #Push
  18. why xSaG?
  19. Thank you everyone for the kind feedback. next build is coming soon. If everything goes as planned we'll hit stable soon. And no, I don't plan on releasing a bin like I do it with the core. Maybe some day in the future but currently there are no plans. I'm also onto the problem with compiling under release mode and I think I found it. Next build should work without any problems in release mode
  20. how to replace devil for using screenshot method?
  21. You need to change you dragon_soul_refine_settings.py with import item default_grade_need_count = [3, 3, 3, 3] default_grade_fee = [30000, 50000, 70000, 100000] default_step_need_count = [4, 3, 2, 1] default_step_fee = [20000, 30000, 40000, 50000] strength_fee = { item.MATERIAL_DS_REFINE_NORMAL : 10000, item.MATERIAL_DS_REFINE_BLESSED : 20000, item.MATERIAL_DS_REFINE_HOLLY : 30000, } # 강화가 어느 단계 까지 가능 한지 # table(GRADE, STEP) = max strength. default_strength_max_table = [ [2, 2, 3, 3, 4], [3, 3, 3, 4, 4], [4, 4, 4, 4, 4], [4, 4, 4, 4, 5], [4, 4, 4, 5, 6], ] # 일단 기획적으로는 strength 강화의 경우, 강화석에 의해 fee가 셋팅되기 때문에, # dragon_soul_refine_info에 넣지 않았다. # (강화석만 넣어도 얼마 필요한지 보일 수 있도록 하기 위해) # 다만 서버에서는 용혼석 타입 별로 강화석 fee를 셋팅할 수 있도록 해놨기 때문에, # 만일 용혼석 별로 강화석 fee를 다르게 하고 싶다면, # 클라 코드를 수정해야할 것이다. default_refine_info = { "grade_need_count" : default_grade_need_count, "grade_fee" : default_grade_fee, "step_need_count" : default_step_need_count, "step_fee" : default_step_fee, "strength_max_table" : default_strength_max_table, } dragon_soul_refine_info = { 11 : default_refine_info, 12 : default_refine_info, 13 : default_refine_info, 14 : default_refine_info, 15 : default_refine_info, 16 : default_refine_info, } and same for dragon_soul_table.txt # 용혼석 테이블들... # TAB 으로 구분되니 엑셀로 볼 것. # vim으로 본다면 탭간 간격을 조정하고 볼 것. (set ts=16 추천) # 큰 따옴표로 묶인 부분은 안 구분. # \" 이딴거 지원 안함. # 용혼석 Vnum에 대한 comment # ITEM VNUM을 10만 자리부터, FEDCBA라고 한다면 # FE : 용혼석 종류. D : 등급 # C : 단계 B : 강화 # A : 여벌의 번호들... # 이 체계에서 벗어나는 용혼석은 용서하지 않을 것이다. # ok? # 용혼석이 너무나도 많기 때문에 Vnum이 중구난방이면, # Special item group에서 group으로 묶어서 처리하기도 힘들고-_-, # VnumHelper.h에서 처리하는 것도 힘들다. -_- # Group 잡는데만 수천줄을 써야할 지도... # Vnum에 체계를 잡아서 자릿수 기반으로 해야만 한다. # Table은 "Group"과 "이름"으로 시작한다. # Table 내부에 또 Table이 있을 수 있다. # 그렇다고 엉뚱한 테이블을 써놓는다고 서버가 인식하는 것은 아니다. # 필요한 테이블은 다음과 같다. # BaseVnums, BaseAttrs, AddtionalAttrs, AttrSettings, UpgradeTable, ImproveTable, # RefineTable, UpgradeMoneys, ImproveTable, RefineMoneys, WeightTable, DurationTable, # DragonHeartExtTable, DragonSoulExtTable # 확률 테이블의 값은 기본적으로 float이다. # 중요 !!!!! # 테이블을 보다 보면 #--#이라 쓰여진 부분이 있는데 절대로 지우지 말것. # # 이건 vnum to 이름 mapping. # 이걸로 특정 vnum의 용혼석이 어떤 종류의 용혼석인지(이름이 뭔지) 알아낸 후, # 그 용혼석에 해당하는 속성을 찾는다. # 또한 여기에 적혀있지 않은 용혼석이 밑에 Group 정의하는 부분에 있다면 # 에러. Group VnumMapper { # 시작 vnum. # 여기서 써야할 부분은 위에 설명한 FE에 해당하는 부분. # FE를 써줄 것 #--# DragonSoulName Type 1 백룡석 11 2 화룡석 12 3 풍룡석 13 4 철룡석 14 5 뇌룡석 15 6 흑룡석 16 } Group BasicApplys { Group 백룡석 { # 1부터 순서대로 부여된다. #--# Apply_Type Apply_value 1 INT 15 2 RESIST_ICE 15 } Group 화룡석 { #--# Apply_Type Apply_value 1 STR 15 2 RESIST_FIRE 15 } Group 풍룡석 { #--# Apply_Type Apply_value 1 MAX_SP 2500 2 RESIST_WIND 15 } Group 철룡석 { #--# Apply_Type Apply_value 1 DEX 15 2 RESIST_EARTH 15 } Group 뇌룡석 { #--# Apply_Type Apply_value 1 MAX_HP 3000 2 RESIST_ELEC 15 } Group 흑룡석 { #--# Apply_Type Apply_value 1 CON 15 2 RESIST_DARK 15 } } Group AdditionalApplys { Group 백룡석 { # 앞의 첫 컬럼은 순서와 관계 없다. 철저히 확률에 따라 속성이 부여될 뿐이다. #--# Apply_Type Apply_value Prob 1 MAGIC_ATT_GRADE 20 15 2 MAGIC_DEF_GRADE 20 15 3 SKILL_DAMAGE_BONUS 20 15 4 SKILL_DEFEND_BONUS 20 15 } Group 화룡석 { #--# Apply_Type Apply_value Prob 1 ATT_BONUS 350 10 2 DEF_BONUS 250 10 3 NORMAL_HIT_DAMAGE_BONUS 20 10 4 NORMAL_HIT_DEFEND_BONUS 20 10 } Group 풍룡석 { #--# Apply_Type Apply_value Prob 1 MAX_HP 3000 10 2 HP_REGEN 20 10 3 STEAL_HP 10 10 4 KILL_HP_RECOVER 10 10 5 MAX_HP_PCT 25 10 } Group 철룡석 { #--# Apply_Type Apply_value Prob 1 ATT_BONUS_TO_WARRIOR 20 10 2 ATT_BONUS_TO_ASSASSIN 20 10 3 ATT_BONUS_TO_SURA 20 10 4 ATT_BONUS_TO_SHAMAN 20 10 5 RESIST_WARRIOR 20 10 6 RESIST_ASSASSIN 20 10 7 RESIST_SURA 20 10 8 RESIST_SHAMAN 20 10 } Group 뇌룡석 { #--# Apply_Type Apply_value Prob 1 MAX_SP 1500 10 2 SP_REGEN 20 10 3 STEAL_SP 20 10 4 KILL_SP_RECOVER 5 10 5 MAX_SP_PCT 25 10 } Group 흑룡석 { #--# Apply_Type Apply_value Prob 1 BLOCK 15 10 2 DODGE 15 10 3 REFLECT_MELEE 15 10 4 RESIST_CRITICAL 15 10 5 RESIST_PENETRATE 15 10 } } # 여기부터 Default를 둔다. # Default 값을 모든 용혼석이 따르고, # 특정 값이 있는 용혼석은 Default를 바탕으로 그 값을 덮어쓴다. # 등급에 따른 속성수 # 단, basis, add_max는 3보다 크면 안된다. Group ApplyNumSettings { Group Default { #--# GRADE_NORMAL GRADE_BRILLIANT GRADE_RARE GRADE_ANCIENT GRADE_LEGENDARY basis 1 1 1 2 2 add_min 0 0 0 0 0 add_max 0 1 2 2 3 } # Group 백룡석 # { # #--# GRADE_NORMAL GRADE_BRILLIANT GRADE_RARE GRADE_ANCIENT GRADE_LEGENDARY # basis 1 1 1 2 2 # } } # 용혼석 가중치 테이블. # 이 테이블에서 값이 0이라면 그 이상의 강화는 불가능하다고 판단한다. Group WeightTables { Group Default { Group GRADE_NORMAL { # 단계 강화 #--# 0 1 2 3 4 5 6 STEP_LOWEST 1 2 3 0 0 0 0 STEP_LOW 2 3 4 0 0 0 0 STEP_MID 3 4 5 6 0 0 0 STEP_HIGH 4 5 6 7 0 0 0 STEP_HIGHEST 5 6 7 8 10 0 0 } Group GRADE_BRILLIANT { STEP_LOWEST 3 4 5 6 0 0 0 STEP_LOW 4 5 6 8 0 0 0 STEP_MID 5 6 8 10 0 0 0 STEP_HIGH 6 8 10 12 15 0 0 STEP_HIGHEST 8 10 12 15 20 0 0 } Group GRADE_RARE { #--# 0 1 2 3 4 5 6 STEP_LOWEST 6 7 9 11 15 0 0 STEP_LOW 7 9 11 15 20 0 0 STEP_MID 9 11 15 20 25 0 0 STEP_HIGH 11 15 20 25 30 0 0 STEP_HIGHEST 15 20 25 30 40 0 0 } Group GRADE_ANCIENT { #--# 0 1 2 3 4 5 6 STEP_LOWEST 10 12 15 18 20 0 0 STEP_LOW 12 15 18 20 25 0 0 STEP_MID 15 18 20 25 35 0 0 STEP_HIGH 18 20 25 35 40 0 0 STEP_HIGHEST 20 25 35 40 60 80 0 } Group GRADE_LEGENDARY { #--# 0 1 2 3 4 5 6 STEP_LOWEST 30 35 40 45 50 0 0 STEP_LOW 35 40 45 50 55 0 0 STEP_MID 40 45 50 55 65 0 0 STEP_HIGH 45 50 55 65 75 90 0 STEP_HIGHEST 50 55 65 75 90 105 120 } } # Group 백룡석 # { # Group GRADE_NORMAL # { # #--# 0 1 2 3 4 5 6 # STEP_LOWEST 10 20 53 0 0 0 0 # STEP_HIGHEST 50 60 37 18 10 0 0 # } # } } # 개량 table Group RefineGradeTables { Group Default { #--# NEED_COUNT FEE GRADE_NORMAL GRADE_BRILLIANT GRADE_RARE GRADE_ANCIENT GRADE_LEGENDARY GRADE_NORMAL 15 3000 0 80 0 0 0 GRADE_BRILLIANT 10 50000 0 0 80 0 0 GRADE_RARE 5 70000 0 0 0 0 100 GRADE_ANCIENT 3 100000 0 0 0 45 55 } } Group RefineStepTables { Group Default { #--# NEED_COUNT FEE STEP_LOWEST STEP_LOW STEP_MID STEP_HIGH STEP_HIGHEST STEP_LOWEST 4 20000 0 100 0 0 0 STEP_LOW 3 30000 0 20 60 0 0 STEP_MID 2 40000 0 0 40 20 0 STEP_HIGH 1 50000 0 0 0 80 20 } } Group RefineStrengthTables { Group Default { # MATERIAL_DS_REFINE_NORMAL : GRADE_NORMAL 강화석 # MATERIAL_DS_REFINE_BLESSED : 축복의 강화석 # MATERIAL_DS_REFINE_HOLLY : 용신의 강화석 #--# FEE 0 1 2 3 4 5 MATERIAL_DS_REFINE_NORMAL 10000 100 80 70 50 30 20 MATERIAL_DS_REFINE_BLESSED 20000 100 88 77 55 33 22 MATERIAL_DS_REFINE_HOLLY 30000 100 90 80 60 40 30 } } # 용심은 100000(임시 vnum)이고, 충전량은 socket (0)에 박아넣는다. # 단, special item group에 vnum 10053으로 정의되어있는 다른 용심들은 Value(0)에 있는 값이 충전량. # 용심 추출 확률 테이블 # 충전량이 0이라는 것은 추출 실패라는 거. Group DragonHeartExtTables { Group Default { #--# 1 2 3 4 5 # 용심 충전량(%) CHARGING 0 5 15 30 50 # 등급과 충전량에 따른 확률 테이블 # 등급 확률 GRADE_NORMAL 100 0 0 0 0 GRADE_BRILLIANT 0 100 0 0 0 GRADE_RARE 0 0 0 100 0 GRADE_ANCIENT 0 0 0 100 0 GRADE_LEGENDARY 0 0 0 0 100 } } # 용혼석 추출 확률 테이블. # 이것도 1, 2안이 있어 통합할 수 있는 방안으로 감. # 추출 확률을 정할 수 있고, 실패 부산물도 정할 수 있음.(0이면 안줌) Group DragonSoulExtTables { Group Default { #실패 부산물 #--# Prob ByProduct GRADE_NORMAL 100 30270 GRADE_BRILLIANT 100 30270 GRADE_RARE 100 30270 GRADE_ANCIENT 100 30270 GRADE_LEGENDARY 100 30270 } }
  22. @Dobrescu Sebastian too much thx men i solved my problem through ur shared
  23. Ask lb-h @Mano
  24. Im trying to isntall the source on the host, did these stepts till now portsnap fetch extract , portsnap fetch update and when i try to cd /usr/ports/devel/gmake && make install clean it says ===> gmake-4.2.1_1 pkg(8) must be version 1.6.0 or greater, but you have 1.5.5. You must upgrade the ports-mgmt/pkg port first. *** [install] Error code 1 Then when i try to pkg install ports-mgmt/pk it says, No active remote repositories configured. Please help fellows
  1. Load more activity