Players cannot be resurrected in the beginning of Azjol-Nerub

[rorshan]

Current Behaviour

Attempting to resurrect a player at the beginning of Azjol-Nerub will give the error message "Target cannot be resurrected". Once players reach the webbed area they are able to resurrect again.

Expected Behaviour

Players should always be able to resurrect other players.

Source

I couldn't find anything about Azjol-Nerub mentioning resurrection being impossible

Steps to reproduce the problem

With 2 characters, one who can resurrect

1. .tele azjol
2. Enter the instance
3. kill one of the character (.die) and ry to resurrect them
4. .revive works for testing
5. Progress through the instance until you reach the webbed area
6. Kill off one of the character and try to resurrect

Extra Notes

I expect the resurrection is disabled for some reason until some part of the Hadronox script has been triggered when players get near him.

AC rev. hash/commit

[13:05:33]AzerothCore rev. f190e29 2025-12-03 12:51:30 +0100 (master branch) (Win64, RelWithDebInfo, Static)
[13:05:33]Connected players: 1. Characters in world: 1.
[13:05:33]Connection peak: 2.
[13:05:33]Server uptime: 13 minute(s) 16 second(s)
[13:05:33]Update time diff: 10ms. Last 500 diffs summary:
[13:05:33]|- Mean: 4ms
[13:05:33]|- Median: 2ms
[13:05:33]|- Percentiles (95, 99, max): 10ms, 19ms, 24ms
[13:05:33]Using SSL version: OpenSSL 3.5.4 30 Sep 2025 (library: OpenSSL 3.5.4 30 Sep 2025)
[13:05:33]Using Boost version: 1.81.0
[13:05:33]Using CMake version: 4.1.2
[13:05:33]Using MySQL version: 80406
[13:05:33]Found MySQL Executable: C:/Program Files/MySQL/MySQL Server 8.4/bin/mysql.exe
[13:05:33]Compiled on: Windows 10.0.19045
[13:05:33]Worldserver listening connections on port 8085
[13:05:33]Realmlist (Realm Id: 1) configured in port 8085
[13:05:33]VMAPs status: Enabled. LineOfSight: true, getHeight: true, indoorCheck: true
[13:05:33]MMAPs status: Enabled
[13:05:34]maps directory located in C:/Azerothcore/build/bin/RelWithDebInfo/Data/maps. Total size: 291014951 bytes
[13:05:34]vmaps directory located in C:/Azerothcore/build/bin/RelWithDebInfo/Data/vmaps. Total size: 657797442 bytes
[13:05:34]mmaps directory located in C:/Azerothcore/build/bin/RelWithDebInfo/Data/mmaps. Total size: 2192760616 bytes
[13:05:34]Default DBC locale: enUS.
[13:05:34]All available DBC locales: enUS zhCN zhTW esES
[13:05:34]Using World DB: ACDB 335.14-dev
[13:05:34]Latest LoginDatabase update: 2025_07_24_00.sql
[13:05:34]Latest CharacterDatabase update: 2025_09_03_00.sql
[13:05:34]Latest WorldDatabase update: 2025_12_02_04.sql
[13:05:34]LoginDatabase queue size: 0
[13:05:34]CharacterDatabase queue size: 0
[13:05:34]WorldDatabase queue size: 0
[13:05:34]No modules are enabled

Operating system

Windows 10 x64

Custom changes or Modules

No response

[Nyeriah]

Happens if watchers are engaged, as the instance is put in combat during the gatewatcher encounter until he dies

[rorshan]

@Nyeriah I don't think this is it. The players are not in combat when I try to resurrect. The issue also persists after Krik'thir the Gatewatcher is killed, and until players reach the webbed area.

[Nyeriah]

Do .instance getbossstate and check what it says

[rorshan]

Entering Azjol
[15:33:55]Changed Channel: [3. LocalDefense - Azjol-Nerub]

Right at the entrance of the instance, players already can't be resurrected.
[15:34:07]Boss id 0 state is 0 (NOT_STARTED).
[15:34:07]Boss id 1 state is 0 (NOT_STARTED).
[15:34:07]Boss id 2 state is 0 (NOT_STARTED).

After a min or so, Hadronox script starts
[15:35:03]Anub'ar Crusher yells: The gate has been breached! Quickly, divert forces to deal with these invaders!
[15:35:12]Boss id 0 state is 0 (NOT_STARTED).
[15:35:12]Boss id 1 state is 1 (IN_PROGRESS).
[15:35:12]Boss id 2 state is 0 (NOT_STARTED).

So I guess it might not even be because of Hadronox.

Edit: After the time it took me to make this post I'm now able to resurrect again and bosstate
[15:39:12]Boss id 0 state is 0 (NOT_STARTED).
[15:39:12]Boss id 1 state is 0 (NOT_STARTED).
[15:39:12]Boss id 2 state is 0 (NOT_STARTED).

That's without moving from the entrance at all.

[rorshan]

After testing a few times it seems to be somewhat inconsistent. Sometimes resurrecting works until the Boss id 1 (Hadronox?) starts. But that doesn't put anyone into combat. Resurrection spells are not greyed out, they just give an error.

[Nyeriah]

So Hadronox is the culprit as it enters combat and that prevents ress, thanks for checking it out

[Nyeriah]

After testing a few times it seems to be somewhat inconsistent. Sometimes resurrecting works until the Boss id 1 (Hadronox?) starts. But that doesn't put anyone into combat. Resurrection spells are not greyed out, they just give an error.

Ress is prevented if the instance encounters is in progress, it doesn’t relate to players being in combat or not