Skip to content

Fix encounter check for Dungeon entry conditions - #31980

Open
Thor1423 wants to merge 1 commit into
TrinityCore:3.3.5from
Thor1423:Thor1423-patch-1
Open

Thor1423 wants to merge 1 commit into
TrinityCore:3.3.5from
Thor1423:Thor1423-patch-1

Conversation

@Thor1423

@Thor1423 Thor1423 commented Aug 20, 2026

Copy link
Copy Markdown

It shouldn't be possible to walk into a 5-man instance while a boss fight is in progress. That’s how it was in the 2009 original, too.
Removing this line causes not only raids but also dungeons to be checked.

Various archive forum posts confirm this.:

https://eu.forums.blizzard.com/en/wow/t/unable-to-zone-in-while-an-encounter-is-in-progess/21536
https://www.reddit.com/r/wow/comments/trtsbp/queue_pop_unable_to_enter_dungeon_due_to/
https://us.forums.blizzard.com/en/wow/t/lfr-cant-zone-me-in-encounter-in-progress/1090020/2

"The restriction is definitely blizzlike for WotLK. In the original 3.3.5a client's GlobalStrings.lua, Blizzard hardcoded TRANSFER_ABORT_ZONE_IN_COMBAT = "You cannot enter the instance while an encounter is in progress.". Whenever the Dungeon Finder (RDF) auto-teleported a replacement player into a 5-man dungeon while the remaining party was in combat, the server sent TRANSFER_ABORT_ZONE_IN_COMBAT and aborted the loading screen. It's handled by the base Map class (MapEncounterInProgress), which applies to both InstanceMap (5-man) and RaidMap inside the engine."

Tests performed:

Testet ingame and works

It shouldn't be possible to walk into a 5-man instance while a boss fight is in progress. That’s how it was in the 2009 original, too.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants