What death costs you
On Easy your items stay with you when you die. On Normal and Hard they drop where you fell, so the walk back is the whole recovery plan.
Dying is cheap on two of the four difficulties and expensive on the others, and the difference is written into the patch notes rather than the tutorial.
Every figure below is checked against Pequi studios announcements or Steam's own endpoints on 2026-11-09.
Dying in Mayday is either cheap or expensive depending on a menu setting, and the game does not tell you which one you are on until it happens.
Cheap or expensive, by setting
On Easy, you keep your items. On Normal and Hard, your gear drops where you died and you have to walk back for it. Casual, added on 7 November, was not covered by a specific death-penalty announcement, so treat it as the forgiving end and check what happens the first time you go down.
That rule was introduced on 6 November, four days after launch. Before that patch, everyone dropped their items regardless of difficulty. A guide written in the first week will disagree with itself for that reason.
Four settings, four outcomes
| Setting | Items on death | Skeletons in a raid | Recovery required |
|---|---|---|---|
| Casual (Very Easy) | Not documented separately | Reduced | Effectively none |
| Easy | Kept | 7 | Respawn and continue |
| Normal | Dropped at death location | Baseline | Walk back to the spot |
| Hard | Dropped at death location | Baseline | Walk back, against harder wildlife |
The interesting column is the second one. Skeleton attacks were reduced from 13 to 7 on Easy on 6 November, which means Easy differs from Normal in encounter size as well as death penalty. The two settings are not the same fight with different numbers.
Where you respawn
You wake up at your camp, which is why camp placement in the first three days matters more than it seems at the time. A camp on the coast is a respawn point that puts you near food and water. A camp inland, chosen for defensibility, is a respawn point in the middle of the thing that killed you.
The one documented respawn oddity is a bug rather than a mechanic: on 6 November a patch fixed an issue where loading a save placed the player inside a cave. That was a load bug, not a death bug, but it produced the same feeling of waking up somewhere you did not choose. Fixed, and the same patch announcement admits it was introduced by the previous fix.
Walking back for your gear
If you are on Normal or Hard and you died somewhere far from camp, the recovery is a real expedition and should be treated as one. Three things make it survivable.
Go armed but travel light. You are not there to gather, you are there to pick up a pile of items. Empty inventory slots are the whole point of the trip.
Go in daylight. Nothing in the published patch notes suggests night makes enemies stronger, but visibility does drop and the walk back is when navigation mistakes happen.
Bring food you can afford to lose. The raft rule applies to walking too: if the recovery trip costs you your remaining food, you have traded one loss for another.
If the death happened on an island you sailed to, the recovery problem is compounded, because the crossing itself costs food. In that case the honest advice is to write off the gear if the island is far and the items are replaceable. Iron is replaceable. A full inventory of tools you spent two days building might be worth one carefully provisioned return trip.
No experience, no timer
Nothing in the achievement list or the patch notes mentions experience loss, a durability penalty applied on death, or a corpse timer, and no patch note has ever mentioned dropped items decaying. The documented death penalty is distance: the walk back.
That makes death cheap in a structural sense. Nothing compounds. The achievement Never Give Up, awarded for dying once, sits at 38.0%, which means more than a third of players have died and the game treats it as a normal part of the experience rather than a failure state.
Starving to Death, 57%
Starving to Death, at 57.0%, is awarded for reaching zero hunger. The description adds a line: "You haven't died yet, but eat something before it's too late." So the achievement is not for dying of hunger, it is for hitting zero on the bar and surviving to notice. Also the clearest signal in the data that hunger is the game's main pressure: 57% of players have bottomed out at least once.
On Easy, that moment costs nothing. On Normal, bottoming out far from camp can start the sequence that ends with a recovery walk.
First minute after dying
The instinct is to run back immediately. On Normal and Hard that instinct is how a single death becomes two.
| Step | Why |
|---|---|
| Note where you were | The map does not mark your corpse; your memory is the marker |
| Check the difficulty | On Easy there is nothing to recover |
| Eat before you move | A recovery trip on an empty bar is a second death |
| Take empty slots, not tools | The trip is a pickup, not a gathering run |
| Go in daylight | Visibility, not enemy strength, is what changes at night |
The fourth row is the one people get wrong. A player who died with a full inventory and walks back with a full inventory has made the trip for nothing, because there is nowhere to put the gear when they arrive.
When to write a death off
A death on a distant island, with an inventory of common materials, is not worth the crossing. The food cost of getting there is real and the materials are replaceable on any beach. The distinction to make is between gear you built and material you gathered: iron ingots are a morning's work, a set of tools you have been carrying since day three is not.
A judgement the game never asks for explicitly, since it does not tell you what you dropped or where. It just leaves you at camp with an empty bag and a decision.
Invisible inventory, 7 November
The 7 November patch fixed an inventory bug: if you died with your inventory open under certain circumstances, the inventory could become invisible or appear out of position afterwards. Fixed now, but an inventory that vanishes after a death on an older build is misrendered rather than gone. Reopening it or reloading corrects the display.