How to run a hardcore Minecraft server

Hardcore is Minecraft with one life. On a server it becomes a shared challenge: everyone plays carefully, every death is an event, and the world keeps going without the people who did not make it. This guide covers setting it up and the decisions you need to make before the first player joins.

Turn it on

Set hardcore=true in server.properties — on Cobbly, in the Properties tab — before the world is created. If your server already has a world, reset it after changing the setting so everyone starts fresh. See How to reset your Minecraft world.

Hardcore locks difficulty to hard. Hearts are drawn with the hardcore texture so players know where they are.

What happens when a player dies

On a multiplayer hardcore server, a player who dies is put into spectator mode: they can fly through the world and watch, but not interact. The world itself carries on for everyone else. Nobody is kicked or banned by the game.

That makes spectators useful — they can scout, keep friends company, or record. Some groups prefer the stricter version where dead players leave; for that, ban them manually with ban Name Died on day 12, or use a plugin that does it.

Reviving a player

There is no “respawn” in hardcore, but an operator can bring someone back with gamemode survival Name in the console. They switch back wherever their spectator camera happens to be — possibly mid-air or inside a cave wall — so teleport them somewhere safe first with tp Name x y z. Whether revives are allowed — and what they cost — is worth agreeing before you start, not after the first death.

Back it up

One bad night, a server crash at the wrong moment, or a griefer can end a hardcore run. Take a manual backup before big fights (the Ender Dragon, raids, the Wither) and keep automatic backups on. Restoring a backup is also the fair way to undo a death caused by lag or a crash rather than a mistake — if the group agrees. How backups work covers both.

Popular variations

• No natural regeneration — gamerule naturalRegeneration false. Health comes back only from golden apples and potions. The UHC rule.
• Shared health or shared lives — needs a plugin or data pack; search for “shared health” for your server type.
• A limited number of lives — a plugin or a scoreboard-based data pack counts deaths and switches players to spectator on the last one.
• Seasons — a hardcore world that runs until everyone is dead, then a new one with a new seed. Keep a download of each finished world for posterity.

Rules that make it work

• Decide on PvP. With PvP on, one argument can end someone’s run. Most hardcore groups turn it off (pvp=false).
• Turn off the sleeping requirement. gamerule playersSleepingPercentage 50 stops one person who is mid-mine keeping everyone out in the night.
• Use a whitelist. A stranger killing players is the worst way for a run to end. See Controlling who can join.
• Agree what counts as “unfair”. Deaths from server lag, crashes and disconnects are the usual argument. Decide beforehand whether those get a restore.

On a host where servers sleep when idle, nothing happens in the world while it sleeps — no mobs, no hunger — so logging off somewhere unsafe is no more dangerous than in single-player.