At The Enemy's Gates
Cannot mount Argent Horses
Once the argent lance is equipped the argent horses should be mountable
Wowhead: https://www.wowhead.com/quest=13855/at-the-enemys-gates
Argent Lance already equipped but can't mount any of the Argent Horses
Video of the bug: https://youtu.be/bCkC2N-ITiE
A couple of my players tested having the same bug on my live server. One of them was able to record a video of the bug: https://youtu.be/bCkC2N-ITiE
Current solution: kill the mobs with your character - (very hard) not doable
master
5bfbb9f
Ubuntu 16/18
We already closed same issue like that
https://github.com/azerothcore/azerothcore-wotlk/issues/1877
Actually i can't reproduce it. I'm able to mount up when having equiped lance. Will leave this open until confirmation from someone else
Well it's a real bug. Please check the video if you haven't seen. Maybe there's something causing this bug. Module perhaps?
I can confirm this issue. If you enter the Court of Bones _without_ a lance equipped you cannot mount the Stabled Campaign Warhorses, even if you equip a lance while being in the Court of Bones. If you enter the area with a lance already equipped you will be able to mount the horses, even if you then switch to another weapon, which is also not correct.
I think this has to be related to the area phasing in and out.
ty for clearing this out stoabrogga, issue authors should be more precise
I can confirm this issue. If you enter the Court of Bones _without_ a lance equipped you cannot mount the Stabled Campaign Warhorses, even if you equip a lance while being in the Court of Bones. If you enter the area with a lance already equipped you will be able to mount the horses, even if you then switch to another weapon, which is also not correct.
I think this has to be related to the area phasing in and out.
Thank you. makes sort of sense now
There's a very old issue that's still open on TC describing exactly the same problem:
https://github.com/TrinityCore/TrinityCore/issues/20935
I think I've found a way to fix this via PR #1936.
@spinzaku i saw your shitty comments, last warning
Most helpful comment
There's a very old issue that's still open on TC describing exactly the same problem:
https://github.com/TrinityCore/TrinityCore/issues/20935