Going down, and dying

Reaching zero health does not kill you. It puts you on the ground, and what happens next is decided by dice in front of everyone watching.

Death saving throws

Once you are down, every five seconds the server rolls a d20 for you.

• 10 or higher is a success.
• Under 10 is a failure.
• A natural 20 counts as two successes. A natural 1 counts as two failures.

Three successes and you stabilise. Three failures and you are dead. It never drags on — six rolls at most, so the whole thing is settled inside about half a minute, and everyone nearby watches each roll land.

Stabilise on your own and you come back at a twentieth of your health. Alive, barely, and in no state to keep fighting.

Anyone can pull you out

You are not only waiting on the dice. Any healing that takes you above zero ends the whole thing immediately — a cleric's spell, a friend with a potion, a healing effect still ticking from before you fell. This is the reason to go down fighting near your party rather than alone.

A familiar with a guardian's instinct may also drag you back, though it can only do that so often.

There is one place none of this applies. Underwater there are no saving throws. An unconscious body cannot swim to the surface, so drowning simply kills you.

What dying costs

Death is not a respawn button. It takes something every time.

• A fifth of the silver you are carrying, gone.
• A tenth of your experience.
• A risk to your Constitution — dying badly can leave a mark.

Bank your silver before anything dangerous. That is what the bank is for.

If a player killed you, your silver does not vanish — they take it. That is the real stake in open-world fighting, and the reason an outlaw is worth hunting.

In a raid

Going down in a raid is survivable, because the rest of your clan is standing right there. Actually dying is counted: three real deaths and you are out for the remainder of the raid, watching the rest of it from the outside.