Jump to content

VladimirMangos

Members
  • Posts

    2813
  • Joined

  • Last visited

    Never
  • Donations

    0.00 GBP 

Everything posted by VladimirMangos

  1. Yes, you find source! I will fix shortly this and other places affected by this.
  2. crash showuo not meaning that bug added in specific changes, it can be just hidden old bug.
  3. I not reject core problem case, but need some repeatable way for testing
  4. "looks like it's deleted from other thread" this is impossible in current core. Diff map-threads not supported... i_path changes only in WaypointMovementGenerator<Creature>::LoadPath and in WaypointMovementGenerator<Creature>::ClearWaypoints() ClearWaypoints called from ReloadPath not used in clean code now. So or object deleted or LoadPath called somewhere But in single thread if Update called this possible only after MovementInform... Where deleting/NULL cases checked....
  5. In DBC at _each_ player client. Not server DBC. In any i close thread because DBC edition not allowed. And you banned for attempt discus DBC edition at this forum...
  6. with clean sources this is impossible: cooldown checked in totem summon spell cast.
  7. Hard say anything by provided crash dump....
  8. Must be fixed in [9412]
  9. no, this will add more
  10. Last crash fixed in [9407]
  11. I already ban some posters and will ban for any DBC edition discussion at this forum...
  12. Fixed in [9404]
  13. possible client side check then...
  14. other player "this". If you don't known what "this" meaning you better read C++ tutorial.
  15. Why use need GetPlayer "this" already pointed to player.
  16. Fixed in [9393]. Thank you. Difference in case: spell1 triggering spell2 that at cast triggering spell3 and so on until spell10... in first case spell11 will fail casted, in second case it will casted and possible triggering one more and at some monent this chain server will crash at stack overflow. I recomment read commit notes before ask any questions... in many cases it have all reqiored info.
  17. This is just common forum policy. Nothing personal
  18. In [9380] and [9382]. Thank you
  19. Please, next time post in own thread. Also this commands have default access mode: admin (3)
  20. we have svn store corruption in some monent...
  21. in [9369]. Thank you
  22. Base at useless unrelated posts from ppl that not understand that just crash and specific problem crash is 2 big different things i ma going to close threads. Threads now totally useless for original task: find and test probklem related to group update related crashes. I not see any infor pointing to existense original problem.
  23. In [9365]. Thank you
×
×
  • Create New...

Important Information

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. Privacy Policy Terms of Use