Can't reproduce this from the code as it stands — there's an explicit invulnerability gate the instant HP hits 0, and every monster-damage path (touch, ranged, traps) already checks it, closing off a second hit landing while you're dead. That guard was added for an earlier report (#210), so if you saw this recently I'd want to know roughly when — it may have been on a build from before that landed. Marking can't-repro for now; please re-file if it happens again and you can note the date.

Correction — this is a real bug and I should not have closed it.

I marked it can't-reproduce because I found a guard in the code that's supposed to make a dead player untouchable, and assumed that settled it. It doesn't — the issue you described is still happening, so there's a hole in that guard that I hadn't found. Reading the code and concluding 'this can't happen' was the wrong call when you'd just watched it happen.

Reopened and confirmed. If you do see it again, the most useful detail would be what killed you the second time (a monster walking into you, versus something like a trap or a ranged attack) — that would narrow down which path is getting through. But don't go hunting for it; you've already done the hard part.

Found it, fixed it, pushed it. You were right that it still happens — and I was looking in completely the wrong place.

The corpse itself really was protected; that's why I couldn't find anything. The hole was in the REVIVE. When you pressed OK, we marked you alive and healed you to 50 HP immediately, and only THEN started loading the town to warp you to — which takes a moment, longer if you've never visited it. For that entire window you were standing alive, damageable, with no invulnerability, on the exact tile you died on, with the monster that killed you still standing on top of you. It hit you, and the whole death sequence ran again — second tomb, second prompt, second EXP penalty — while the first warp was still loading underneath it. That matches your description exactly, including the animation replaying.

The reference server does it the other way round: it warps you first and heals you second, and there's a comment in its source noting this exact bug. We now do the same — nothing marks you alive until the destination map is actually up — plus three extra guards so no damage path can reach a dead player.

To re-test: die somewhere with monsters standing right on you and press OK. You should warp out cleanly with no second death.

Fixed and shipped.

The corpse itself was gated — the hole was in respawn(). It cleared the death flags and healed you to 50, and THEN kicked off an async load of the town map (map JSON plus CDN textures). For that whole window your character stood alive and damageable, with no invincibility frames, on the tile you died on, with the killer still standing on top of you. Hence dying again while already dead, animation and all.

Cosmic does it in the opposite order — changeMap(returnMap) at Character.java:7569 BEFORE updateHp(50) at :7576 — and the comment right above it says, literally, that players could otherwise revive in the area and take damage before returning to town. Everything that makes you alive now runs only once the destination map is up, and it is idempotent, plus three defence-in-depth gates behind it.

LIVE on the published build.