Nyeriah
commented
5 days ago From what I understand of this, the issue is that raids also get locked when you reach the 5 dungeons mark. We don't intend to mirror classic changes, just original 335 data
Open balleny opened 3 months ago
Nyeriah
commented
5 days ago From what I understand of this, the issue is that raids also get locked when you reach the 5 dungeons mark. We don't intend to mirror classic changes, just original 335 data
What client do you play on?
enUS
Faction
Both
Content Phase:
Generic
Current Behaviour
you can run 5 dungeons before getting a dungeon lockout this may or may not include raids
Expected Blizzlike Behaviour
Blizzard made a few changes during wotlk classic. Depending on what AZ is striving for, we either need to make some fixes (vanilla) or modifications (classic):
chromiecraft/AZ: 5 dungeons or raids, then locked for both dungeons and raids vanilla wotlk: 5 dungeons, raids not affected (even if dungeon locked, you could enter raids) classic wotlk: 10 dungeons or raids per hour, then both locked
RDF queue should not affect that lockout except for that specific dungeon (this kinda contradicts the previous part, but I didnt found a good source right now. Best, would likely to look through the code of the wow addon NovaInstancetracker)
additionally, wotlk classic added a 30 dungeons per day lockout to prevent botting
Source
https://www.wowhead.com/wotlk/news/changes-for-raid-lockout-resets-in-wrath-classic-329004 https://us.forums.blizzard.com/en/wow/t/dungeons-lockout-how-it-work-in-classic/263922/9
best would likely to check the addon NovaInstancetracker
( https://us.battle.net/support/en/article/10994 was changed by https://www.wowhead.com/wotlk/news/changes-for-raid-lockout-resets-in-wrath-classic-329004?webhook )
Steps to reproduce the problem
.
Extra Notes
No response
AC rev. hash/commit
https://github.com/chromiecraft/azerothcore-wotlk/commit/482f4c94ffdb9cd859482d977aa31a18a60ef8d9
Operating system
Ubuntu 20.04
Modules
Customizations
None
Server
ChromieCraft