Jump to content

Bug Tracker Activity

Showing bugs posted in for the last 365 days.

This stream auto-updates     

  1. Today
  2. http://www.wowhead.com/quest=5624

    Oh olion i got It. Realy thanks for class here about game structure. Yep i figure out the error as vprintf its a mesa with C strings and std strings. I really apreceiated u Lost ir time explaing tô me . Now i Will delete repo and clone again with This args you Said.
  3. http://www.wowhead.com/quest=5624

    Alright, let's analyze the log together. We start, for example, from record #4. Spell.cpp:1128 : { ((Creature*)unit)->AI()->SpellHit(m_caster, m_spellInfo); } The SpellHit method appears on the next record, #3, as a deeper one in the calling sequence. npcs_special.cpp:1108 : ((Player*)pCaster)->TalkedToCreature(m_creature->GetEntry(), m_creature->GetObjectGuid()); The next method in the stack trace (from record #2), Log::outString(), is not referenced here. But wait, maybe one of the two RHS methods, GetEntry() or GetObjectGuid(), was compiled inline and calls the log? Look at Object.h: 150 ObjectGuid const& GetObjectGuid() const { return GetGuidValue(OBJECT_FIELD_GUID); } 155 uint32 GetEntry() const { return GetUInt32Value(OBJECT_FIELD_ENTRY); } None of the methods is defined as virtual, they may not be (and actually are not) overridden. Also, these methods are far too popular to have any logging inside. The Player::TalkedToCreature() method is too long to be auto-inlined by any sane compiler (and does not contain logging anyway). The only conclusion left to us, is that some s**t happened at npcs_special.cpp:1108. At this point I cannot help further except by a hint. Do "a fresh clone" only into an empty directory, not forgetting --recursive parameter. P.S. The usual cause of such crash is the difference between std::string and C string. The later is awaited by any C print(). So, to print GUID for example, you need the c_str() conversion: GetGuidStr().c_str();
  4. http://www.wowhead.com/quest=5624

    Cleam git clone, made changes but still same problem. #0 0x00007ffff5861cfb in vfprintf () from /lib64/libc.so.6 #1 0x0000555556611d0b in vutf8printf (out=0x7ffff5bb75a0 <_IO_2_1_stdout_>, str=0x555556bd77f7 "Player GUID : %s", ap=0x7fffed1766a0) at /home/jefferson/wowserver/getmangos/serverZero/src/shared/Utilities/Util.cpp:495 #2 0x0000555556609fa2 in Log::outString (this=0x555557184fc0, str=0x555556bd77f7 "Player GUID : %s") at /home/jefferson/wowserver/getmangos/serverZero/src/shared/Log/Log.cpp:398 #3 0x00005555568f5a4d in npc_garments_of_quests::npc_garments_of_questsAI::SpellHit (this=0x7fffc6838fc0, pCaster=0x7fffc6c3b300, pSpell=0x7fffe32b5290) at /home/jefferson/wowserver/getmangos/serverZero/src/modules/SD3/scripts/world/npcs_special.cpp:1108 #4 0x00005555563ac63d in Spell::DoAllEffectOnTarget (this=0x7fffd4262f20, target=0x7fffd4003620) at /home/jefferson/wowserver/getmangos/serverZero/src/game/WorldHandlers/Spell.cpp:1128 #5 0x00005555563b3366 in Spell::handle_immediate (this=0x7fffd4262f20) at /home/jefferson/wowserver/getmangos/serverZero/src/game/WorldHandlers/Spell.cpp:2891 #6 0x00005555563b31e4 in Spell::cast (this=0x7fffd4262f20, skipCheck=false) at /home/jefferson/wowserver/getmangos/serverZero/src/game/WorldHandlers/Spell.cpp:2871 #7 0x00005555563b40c3 in Spell::update (this=0x7fffd4262f20, difftime=100) at /home/jefferson/wowserver/getmangos/serverZero/src/game/WorldHandlers/Spell.cpp:3101 #8 0x00005555563bfe5d in SpellEvent::Execute (this=0x7fffd40053c0, e_time=21275, p_time=100) at /home/jefferson/wowserver/getmangos/serverZero/src/game/WorldHandlers/Spell.cpp:6410 #9 0x0000555556615842 in EventProcessor::Update (this=0x7fffc6c3b478, p_time=100) at /home/jefferson/wowserver/getmangos/serverZero/src/framework/Utilities/EventProcessor.cpp:53 #10 0x00005555561b1e66 in Unit::Update (this=0x7fffc6c3b300, update_diff=100, p_time=100) at /home/jefferson/wowserver/getmangos/serverZero/src/game/Object/Unit.cpp:318 #11 0x00005555560db577 in Player::Update (this=0x7fffc6c3b300, update_diff=100, p_time=100) at /home/jefferson/wowserver/getmangos/serverZero/src/game/Object/Player.cpp:1149 #12 0x00005555562e2edd in WorldObject::UpdateHelper::Update (this=0x7fffed176d20, time_diff=100) at /home/jefferson/wowserver/getmangos/serverZero/src/game/Object/Object.h:467 #13 0x00005555563171b1 in Map::Update (this=0x55555b3d1530, [email protected]: 100) at /home/jefferson/wowserver/getmangos/serverZero/src/game/WorldHandlers/Map.cpp:534 #14 0x00005555564c6480 in MapUpdateRequest::call (this=0x7fffc71b8f30) at /home/jefferson/wowserver/getmangos/serverZero/src/game/Maps/MapUpdater.cpp:50 #15 0x000055555660d547 in DelayExecutor::svc (this=0x55555b510450) at /home/jefferson/wowserver/getmangos/serverZero/src/shared/Threading/DelayExecutor.cpp:67 #16 0x00007ffff773eac4 in ACE_Task_Base::svc_run (args=0x55555b510450) at /home/jefferson/wowserver/getmangos/serverZero/dep/acelite/ace/Task.cpp:260 #17 0x00007ffff773f2d2 in ACE_Thread_Adapter::invoke_i (this=0x55555b510c20) at /home/jefferson/wowserver/getmangos/serverZero/dep/acelite/ace/Thread_Adapter.cpp:161 #18 0x00007ffff773f164 in ACE_Thread_Adapter::invoke (this=0x55555b510c20) at /home/jefferson/wowserver/getmangos/serverZero/dep/acelite/ace/Thread_Adapter.cpp:96 #19 0x00007ffff7654edf in ace_thread_adapter (args=0x55555b510c20) at /home/jefferson/wowserver/getmangos/serverZero/dep/acelite/ace/Base_Thread_Adapter.cpp:126 #20 0x00007ffff5bc3280 in start_thread () from /lib64/libpthread.so.0 #21 0x00007ffff5906f9d in clone () from /lib64/libc.so.6
  5. flight

    * When learning flying in Azzaroth it does not allow you to fly strait away. * you need to log out and back in to fly * when dismount and try to fly again you are unable
  6. Yesterday
  7. http://www.wowhead.com/quest=5624

    This is your custom logging in the SD3 script. Just take the original npcs_special.cpp and change only Player.cpp as described above.
  8. http://www.wowhead.com/quest=5624

    Thread 5 "mangosd" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffed979700 (LWP 6870)] 0x00007ffff5861cfb in vfprintf () from /lib64/libc.so.6 looking forward to see whats happen. using gdb backtrace.txt
  9. http://www.wowhead.com/quest=5624

    Sorry i didint see this commit, i will try apply and see if works. Tnx Olion and Necrovoice
  10. SELECT * FROM `gameobject` WHERE `id`=375; There are 10 GOs spawned with respawn time 6 minutes. The quest objective is 10 items (= 10 GO uses), thus we really have insufficient GOs and/or too long respawn time. The decision can be made with a movie about the quest. Extremely simple DB issue.
  11. http://www.wowhead.com/quest=5624

    This refactoring commit was inaccurate and had killed the Player::TalkedToCreature( method giving KC. To fix it, remove this line containing { continue; } which was erroneously left of a removed conditional operator.
  12. http://www.wowhead.com/quest=5624

    Yes, i will try fix the way player will be rewarded, and if i got any result, i will post here.
  13. http://www.wowhead.com/quest=5624

    It works on m1 and M2 if that helps you.
  14. http://www.wowhead.com/quest=5624

    If we give .die on npc, we got credit. I think its a miss understand im SD3 scripts. i tring debug with Linux and WIndows
  15. http://www.wowhead.com/quest=5624

    Looking into this. The quest works as intended with correct spells Lesser heal (Rank2), Power Word: Fortitude(Rank1). The NPC will respond and run away.. quest credit is whats lacking here.
  16. Last week
  17. 5 man run in Shadowfang - and most of the party were permanently stuck in combat. Healing a char who was stuck in combat caused the healer to be also stuck in combat, so drinking / regainign mana is near impossible. The issue *might* be related to the "Haunted" debuff, as this never caused any of the mobs to visibly spawn, possible these did spawn and were the cause the combat flag..... thats a guess
  18. http://www.wowhead.com/quest=5624

    Changed Status to Confirmed
  19. http://www.wowhead.com/quest=5624

    Still same as me. Do all script stuff, and he fade way. player dont get quest complete. Or if we .kill on npc. quest is completed.
  20. Gist of problem: Hunter Survival talent 'Entrapment' procs off ANY source of damage over time, and does not trigger from Frost Trap as it should. Found/tested on: Covenant WoW - Using World DB: Version: 21, Structure: 14, Content: 67 Entrapment 5/5: Gives your Immolation Trap, Frost Trap, and Explosive Trap a 25% chance to entrap the target, preventing them from moving for 5 sec. What does work: Immolation Trap and Explosive Trap both trigger the talent correctly, allowing multiple entrapments per damage over time effect. Entrapment is not affected by diminishing returns on Zero and this is correct as diminishing returns were not added to the talent until Burning Crusade: Source What does not work: Frost Trap does not trigger Entrapment at all, and it should be able to trigger entrapment multiple times with a chance each 'pulse' if the enemy stays within the frost AoE. What is working incorrectly: Entrapment is triggering off ANY source of damage over time including hunter stings, and trinkets such as 'Chained Essence of Eranikus'. Proof of use: Plops PvP video on Youtube This video is from a 2006 Hunter pvp showcase by Plops, who can be found at Warcraft Movies here Timestamps: 0:37 Frost Trap activates 0:47 Rogue is entrapped - 1:10 Frost Trap activates 1:13 Warrior is entrapped 1:20 Warlock is entrapped 1:31 Warlock is entrapped a second time
  21. The pumpkins for the quest "Fields of Grief" do not respawn or have a VERY long spawn time
  22. As shown here, there seems to be an issue with underwater pathfinding
  23. Some Lazy Peons just don't move and will not respond to the foreman's blackjack and will not go to sleep
  24. item Item has been looted bug

    Indeed you are correct. I was unable to reproduce this bug or anything like it in M1 or M2.
  25. When attempting to start the chicken quest in westfall, players are unable to actually accept the quest even with the chicken feed Tested on two separate accounts with entirely different people
  26. item Item has been looted bug

    https://github.com/mangoszero/server/pull/51 I apologize for the bug I've introduced here about 2 months ago. The slot ID issue is gone with this revert, but quest loot from the original report is to be tested still. It should not be relevant for other cores.
  27. Earlier
  28. item Item has been looted bug

    This bug also exists when looting chests of all kinds (chests, crates, etc.) You can be grouped or solo to reproduce this. Start looting a chest and let the loot window open Take any 1 item Close the loot window, jump, or move (just close the window) When you attempt to recover the items, you will get the "Already looted" error The item you are trying to loot may display a different icon when you close and re-open the chest I did not test all loot slots as in a situation where there are 2-3 pages of loot, but it appears to be any item you take will work. The loot type does not seem to matter, and the source of the loot window does not seem to matter (mobs, chests, crates and so on all work the same). I have NOT tested resource nodes yet but will edit this when I do. I was also able to bug my loot entirely by jumping and moving forward with the loot window open, but this is not a 100% occurrence (I had to delete WTF and WDB to fix the issue). Being feared away from a loot source will also cause this bug if you have taken an item from the chest. Shift+click (autoloot all items) normally as long as you have not bugged the chest first. There is something else I wanted to add, but I will edit it in after more testing. This bug may also be in Mangos 1 and 2.
  29. item Item has been looted bug

    Another screenshot to confirm. You can see in the log the item i just removed and closed the loot window and then attempted to get another.
  1. Load more activity

Contact Us

To contact us click here
You can also email us at [email protected]

Privacy Policy | Terms & Conditions

Repositories

The Link to the master list
of MaNGOS repositories:
Copyright © getMaNGOS. All rights Reserved.

This website is in no way associated with or endorsed by Blizzard Entertainment®
×