Jump to content
metin2dev

.NyanCat

Members
  • Content count

    16
  • Joined

  • Last visited

Community Reputation

0 Neutral

About .NyanCat

  • Rank
    Neutral

Profile Information

  • Gender
    Male

Recent Profile Visitors

516 profile views
  1. .NyanCat

    c++ Fix Moblock/bravery cape hack

    I tried everything out now and both wait and pro damage are fixed. Moblock as well! Nice! Is there a solution for move speedhack?
  2. .NyanCat

    c++ Fix Moblock/bravery cape hack

    Can you send me the link to the fix? Maybe instead of banning just kick the players?
  3. .NyanCat

    c++ Fix Moblock/bravery cape hack

    Can you create a guide for all types of cheats? What about Pro/Wait Damage? Speedhacks? Wallhack?
  4. Any updates? There is a core down in the uniqueKill Funktion which is called in char_battle.cpp. The down appears on very heavy loads with many plaeyrs. Greets
  5. Wow thanks guys for your help! @Yiv: With your first solution the core crashed after about 22 hours. But without generating the .core file so i cant backtrace the error... @Socialized Im gonna try the modification now and tell you if the crashes are gone. Thanks again!
  6. Hey thanks for your help! Do you think that i can implement it right into the live system? The problem is that it only occures on the live server. The test server does not have this problems. The files are 1:1 the same except the database (much more players on live) I cant figure out the excact problem are these timers saved somewhere in the database? Greetings and thanks for your help!
  7. .NyanCat

    [Syserr] Game core crash

    up still the same
  8. Hello everybody! My channel cores randomly crash with this error. #0 0x081d7a53 in quest::CQuestManager::CancelServerTimers () #1 0x08104e07 in CDungeonManager::Destroy () #2 0x08104bc9 in dungeon_dead_event () #3 0x081587eb in event_process () #4 0x08172c2c in heartbeat () #5 0x08174b73 in idle () #6 0x08173655 in main () Any Ideas?
  9. .NyanCat

    [Syserr] Game core crash

    Does anyone have a solution for this? Maybe @Vanilla? -> I use your latest core. #Edit: Latest Core dump #0 0x081d7a53 in quest::CQuestManager::CancelServerTimers () [New Thread 29814900 (LWP 100163/<unknown>)] [New Thread 29814600 (LWP 100159/<unknown>)] [New Thread 29814300 (LWP 100158/<unknown>)] [New Thread 29814000 (LWP 100076/<unknown>)] (gdb) bt #0 0x081d7a53 in quest::CQuestManager::CancelServerTimers () #1 0x08104e07 in CDungeonManager::Destroy () #2 0x08104bc9 in dungeon_dead_event () #3 0x081587eb in event_process () #4 0x08172c2c in heartbeat () #5 0x08174b73 in idle () #6 0x08173655 in main () btw .core file has 1.8gb!
  10. I have the same problem. Can you tell us what exacly to do? I do run a 64bit os (FreeBSD 11+)
  11. Hey please send me your skype addy. Im interested in the pro version
  12. .NyanCat

    Very clean 40k client.

    Reup please
  13. I think your problem is caused from a missmatch of the sequence tables of server bin and client bin. Try this http://www.elitepvpers.com/forum/metin2-pserver-guides-strategies/2924143-release-how-sequencetable-ndern.html Eng.: https://metin2dev.org/board/index.php?/topic/896-sequence-table-patcher-by-tyrar/ DL: deadlinks.rar No credits for me! All credits go to Tyrar for SequencePatcher and blackyuko for the dif-patcher
×