Jump to content

Firecracker

Inactive Member
  • Posts

    39
  • Joined

  • Last visited

  • Feedback

    0%

Everything posted by Firecracker

  1. Hi devs, one of my game's core crashed an hour ago. This is core debug bt. Do you have any idea what is the problem? #0 0x288f68d7 in thr_kill () from /usr/lib32/libc.so.7 #1 0x288f68ca in raise () from /usr/lib32/libc.so.7 #2 0x288f6816 in abort () from /usr/lib32/libc.so.7 #3 0x2874f595 in __gnu_cxx::__verbose_terminate_handler () at ../../.././../gcc-4.8-20131212/libstdc++-v3/libsupc++/vterminate.cc:95 #4 0x2874c295 in __cxxabiv1::__terminate ( handler=0x2874f400 <__gnu_cxx::__verbose_terminate_handler()>) at ../../.././../gcc-4.8-20131212/libstdc++-v3/libsupc++/eh_terminate.cc:38 #5 0x2874c2ef in std::terminate () at ../../.././../gcc-4.8-20131212/libstdc++-v3/libsupc++/eh_terminate.cc:48 #6 0x2874c54e in __cxxabiv1::__cxa_throw (obj=0x6cc600a0, tinfo= 0x86b7460 <typeinfo for std::bad_alloc@@GLIBCXX_3.4>, dest=0x804ddf0 <std::bad_alloc::~bad_alloc()@plt>) at ../../.././../gcc-4.8-20131212/libstdc++-v3/libsupc++/eh_throw.cc:84 #7 0x2874dafe in operator new (sz=sz@entry=12120) at ../../.././../gcc-4.8-20131212/libstdc++-v3/libsupc++/new_op.cc:56 #8 0x080af313 in CHARACTER_MANAGER::CreateCharacter (this=0xffffbe58, name=name@entry=0x2a3e6b9d "G\374\347l\374 Yabani Deli", dwPID=dwPID@entry=0) at char_manager.cpp:84 #9 0x080afda9 in CHARACTER_MANAGER::SpawnMob (this=this@entry=0xffffbe58, dwVnum=dwVnum@entry=552, lMapIndex=lMapIndex@entry=43, x=x@entry=898133, y=289388, z=z@entry=0, bSpawnMotion=bSpawnMotion@entry=false, iRot=iRot@entry=-1, bShow=bShow@entry=true) at char_manager.cpp:419 ---Type <return> to continue, or q <return> to quit--- #10 0x080b01ca in CHARACTER_MANAGER::SpawnMobRange (this=this@entry=0xffffbe58, dwVnum=552, lMapIndex=lMapIndex@entry=43, sx=sx@entry=896800, sy=sy@entry=288100, ex=ex@entry=898800, ey=ey@entry=290100, bIsException=bIsException@entry=true, bSpawnMotion=<optimized out>, bSpawnMotion@entry=false, bAggressive=bAggressive@entry=false) at char_manager.cpp:470 #11 0x080b067d in CHARACTER_MANAGER::SpawnGroup (this=this@entry=0xffffbe58, dwVnum=552, lMapIndex=lMapIndex@entry=43, sx=sx@entry=896800, sy=sy@entry=288100, ex=ex@entry=898800, ey=ey@entry=290100, pkRegen=pkRegen@entry=0x3acb3480, bAggressive_=bAggressive_@entry=false, pDungeon=pDungeon@entry=0x0) at char_manager.cpp:600 #12 0x080b08f3 in CHARACTER_MANAGER::SpawnGroupGroup (this=0xffffbe58, dwVnum=204, lMapIndex=43, sx=896800, sy=288100, ex=898800, ey=290100, pkRegen=0x3acb3480, bAggressive_=bAggressive_@entry=false, pDungeon=pDungeon@entry=0x0) at char_manager.cpp:561 #13 0x081b0937 in regen_spawn (regen=regen@entry=0x3acb3480, bOnce=bOnce@entry=false) at regen.cpp:385 #14 0x081b09e2 in regen_event (event=..., processing_time=1000) at regen.cpp:616 #15 0x0810829d in event_process (pulse=pulse@entry=3684235) at event.cpp:140 #16 0x08210fde in heartbeat (ht=0x2913e550, pulse=pulse@entry=3684235) at main.cpp:251 #17 0x082120aa in idle () at main.cpp:972 #18 0x08054b9d in main (argc=1, argv=0xffffdc28) at main.cpp:640
  2. Actually i dont have lag but some users of my server have lag on their client. Their pc also has good fetures but they get lag. So i cant find any problem. Can it be because of all libs getting from autopatcher for every login?
  3. Hi devs, İ have problem with switchbot. When switch bot starts to change item's bonuses, client get lag seriously. when i open 2. inventory window, lag is gone. Do you have any idea what causes this lag?
  4. check dum_multiply on mob_proto. if it is 0, max damage and min damage are inefficient.
  5. i tried for example: find_npc_by_vnum(101) but it didnt work. is there any way to use this function for mobs? or can we make a function for monsters like that?
  6. system tried old log files but there was not any files. it is not important.
  7. Yeah i saw that topic but i cant understand french. thanks for your response.
  8. hi devs, i realized that there is regen type which is called REGEN_TYPE_EXCEPTION. normally we use regen types like that. g ..... bla bla bla r ..... bla bla bla m ..... bla bla bla but there is another regen type: REGEN_TYPE_EXCEPTION i think we can use like: e ..... bla bla bla but i dont know what it's function is. Do you know what is it's function?
  9. hi devs, my client suddenly close after login and i get ?????????? error. This is my log.txt. There is nothing special i think. I didnt understand this errors. Is there any way which gives information about causes of errors? btw i got this errors after adding sash system with scale.
  10. i missed it. thank you!
  11. hi guys i need sash models for wolfman. i searched on board but all links were gone. could anyone upload them for me?
  12. i realized that ItemCache uses item id not player id. i have to use ItemCacheSet. with this TItemCacheSet * pkItemCache = GetItemCacheSet(packet->player_id); if (pkItemCache) { sys_log(0, "PLAYER_DELETE FAILED HAS BINDED ITEM PID: %d", packet->player_id); peer->EncodeHeader(HEADER_DG_PLAYER_DELETE_FAILED, dwHandle, 1); peer->EncodeBYTE(packet->account_index); return; } i checked that there are some items which are belong to the player who tries to delete character. i want to check that is there any item which is soul binded. but i failed.
  13. hi dev, i want to check player's items if they are binded or not before deleting character. i have added a function which checks item.sql table but cache is problem. i used this to check cache in clientmanagerplayer.cpp but it doesn't work. could anyone help me? CItemCache * pkItemCache = GetItemCache(packet->player_id); if (pkItemCache) { TPlayerItem * pTab2 = pkItemCache->Get(); if (pTab2->bind > 0) { sys_log(0, "PLAYER DELETE FAILED HAS BINDED ITEM PID %d", packet->player_id); peer->EncodeHeader(HEADER_DG_PLAYER_DELETE_FAILED, dwHandle, 1); peer->EncodeBYTE(packet->account_index); return; } }
×
×
  • Create New...

Important Information

Terms of Use / Privacy Policy / Guidelines / We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.