Open strelok076 opened 1 year ago
UPDATE: You can actually capture the flag if you move fast enough and the enemy team does not manage to claim yours. It seems there is a bug with returning your flag after killing the carrier, even if it is sometimes visually returned back to the base the game does not know that. But worse than that is error 132 in battlegrounds...
Hello, thanks for report. If you play BG more, can you please take a look at team members (e.g. make a screenshot of scores when all bots are in) and check if 132 game crash happens only if there are rogues or Shadow priests in BG
I played a game and this is what happened:
Yes, rogues and shadow priests are in the game.
My team can't capture the flag because we previously reclaimed our flag back from the horde and the game thinks they still have it.
I had 3 game crashes during the match.
Only rushing the enemy flag can get you a win, before yours gets claimed at least once, it does not matter if you reclaim it.
Thank you very much for your detailed reports
Gladly, Should I post all the little bugs that I find ?
Hello, sadly our team that works on that repack don't have lot of time to work on core/db (non bots) bugs, unless they ruin bot experience somehow. That BG and 132 crash are definitely type of bugs we will work on fixing, thanks to your info. For other things we usually rely on cmangos team updates, unless we really want to fix some detail.
Understood, thank you for looking into this and hopefully the 132 error especially will be resolved, it ruins pvp at the moment. It also can happen in dungeons when bots are in the party but not as often as battlegrounds.
On newest beta version i played WSG and i didnt had any problem with flag and my flag was reclaimed many times. There was some flag fix.
It is not possible for the flag to be captured in Wsg Wotlk, bringing the enemy flag back to your base does nothing, same for the enemy team, so the score stays always 0-0. Is there a fix for this ? Thank you.