You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
messages not shown for capturing/loosing base/flag - looks to be an issue server side finding broadcast text - appears vmangos and TC use different id's.
WSG:
Cannot return flag
looks to be related to areatriggers that used to exist in .dbc files, but no longer exist in .db2 (fixed using area trigger hotfix)
looks to have a similiar issue to classic, where the flag will remain attached to a character for a few seconds after dropping/returning.
AB:
All flag states showing at same time
both alliance and horde environment states showing at same time
AV:
bg stats broken - likely packet issue
no towers status at top (maybe not part of classic anyway?)
duplicated mobs
duplicated flags
The text was updated successfully, but these errors were encountered:
Some of the bugs here look to be from differences in how vmangos vs TC implement battlegrounds.
e.g vmangos uses db fro gameobjects, but TC uses C++ code.
Will be favouring TC implementation to resolve.
Now possible to queue a battle ground.
remaining issues:
Win / Loss dialog not shown once BG ends.aa7796cgates duplicatedWSG:
Cannot return flaglooks to be related to areatriggers that used to exist in .dbc files, but no longer exist in .db2(fixed using area trigger hotfix)AB:
All flag states showing at same timeAV:
bg stats broken - likely packet issueThe text was updated successfully, but these errors were encountered: