Monster does not die and continues to fight with zero HP #393
Labels
No labels
area
blabot
area
client
area
encounters
area
launcher
area
missions
area
npc-behavior
area
performance
area
portal
area
quests
area
rdb
area
teams
area
trading
area
zone
priority
1
priority
2
priority
3
priority
4
shadowlands
state
cant-reproduce
state
duplicate
state
fixed
state
new
state
unrefined
state
verified
state
wontfix
type
bug
type
enhancement
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: prk/issues#393
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Some monsters, when reduced to zero HP, do not actually die, and instead stay alive and can even continue to follow you around and attempt to continue fighting you.
If you encounter a monster with this issue, please comment below with the name of the monster and also ideally the coordinates for where it can be found, roughly (the output from Shift+F9). Thanks!
Original issue below
While fighting through totw, it appears that very specific named mobs become "zombies". When viewing with debug on, they are marked as dead but continue to follow you.
Named mobs affected:
"windcaller donnel"
"windcaller yatila"
Extended location information:
Server id: 102079, character id: 50000:639, time: 2023-12-28 06:46:16 (UTC)
Version: 00.3.6_EP1, map id: NOT FOUND, build: 52606.
"windcaller yen"
Extended location information:
Server id: 1, character id: 50000:639, time: 2023-12-28 06:44:20 (UTC)
Version: 00.3.6_EP1, map id: NOT FOUND, build: 52606.
"windcaller rendal"
Extended location information:
Server id: 1, character id: 50000:639, time: 2023-12-28 06:44:55 (UTC)
Version: 00.3.6_EP1, map id: NOT FOUND, build: 52606.
"windcaller tilla"
Extended location information:
Server id: 639, character id: 50000:639, time: 2023-12-28 06:53:11 (UTC)
Version: 00.3.6_EP1, map id: NOT FOUND, build: 52606.
"The Re-Animator"
Extended location information:
Server id: 639, character id: 50000:639, time: 2023-12-28 06:46:57 (UTC)
Version: 00.3.6_EP1, map id: NOT FOUND, build: 52606.
"acolyte seleen"
Extended location information:
Server id: 1, character id: 50000:639, time: 2023-12-28 07:04:25 (UTC)
Version: 00.3.6_EP1, map id: NOT FOUND, build: 52606.
shadowfade armor or books
https://www.ao-universe.com/guides/classic-ao/location-guides-5/temple-of-three-winds-loot-table
i am at entrance first mob; and he is killing cacodemon lvl 200 :O cultist lvl 31



Definitely a problem! Please open as a new case, not as a comment in another case 😁
Seems to still be occurring - issues #501 and #503 are instances of this. (Windcaller Donna, Guardian of Time and the Curator)
I saw the same instance of this problem in other instances as well, so wouldn't connect this only to TOTW, with the Vergil in subway behaving in the same manner (e.g. not killable).
Yeah, I've renamed the issue - it's a broad problem when a monster has invalid loot. If you find any instances, comment them here and we'll fix them up
Encountered this issue in Formans - Bodyguards in Director's room (who BTW is not there):
Bodyguard fights until he reaches 0HP, then pauses fighting, resumes when he replenishes a few HP.
Shift+F9 output:
(23:08) Extended location information:
(23:08) - 376.1, 374.9, 46.0 (376.1 374.9 y 46.0 1941)
(23:08) - Pf Proxy: Model=51100:1941 GS=0 SG=0 R=1941, resource: 1941
(23:08) - zone: 41, area: "Area"
(23:08) Server id: 113743, character id: 50000:789, time: 2024-01-17 22:08:21 (UTC)
(23:08) Version: 00.4.5_EP1, map id: NOT FOUND, build: 52606.
I did /set debug 1 on an npc where this happened, and it looks like this:
With /getfull (of npc) looking like this before dead state;
With /getfull (of npc) looking like this when in dead state;
Whereas an NPC that is "killed" will have the following output:
all the while attacking me and me being able to attack it..... after a while the state goes back to:

An example of how it should work vs... bugged npc:
https://imgur.com/a/DuEJk7q
I think this issue is now broadly resolved, though I don't know for sure. Would appreciate a second look at it!
Confirmed fixed.