UHC Server Setup From Scratch: Ultra Hardcore Without Regen Guide

UHC is a format where health does not regenerate naturally. Want to heal? Eat a golden apple or chug an instant health potion. Otherwise it looks like vanilla survival, but with a fixed match time, a shrinking world border and a guaranteed final fight. Let's walk through how to put one together, which plugins to use and how to keep the balance from breaking on day one.

What UHC Is and How It Differs From Hardcore

Hardcore SMP is a long season with one life per player, sometimes lasting months. UHC (Ultra Hardcore) is a short 60-90 minute match where you also have one life, but natural regeneration is off and a shrinking border forces everyone toward the center. After about an hour players physically cannot avoid each other - the border pushes them in, and the final fight begins.

The key difference: in UHC death just ends the match for you, no week-long ban. After the round the server resets the world, picks new teams and starts again. The format works well for streams and tournaments: predictable length, clear rules, defined winner.

In practice the entire mechanic rests on a single gamerule:

/gamerule naturalRegeneration false

After that you can only heal through golden apples, instant health splash potions, regeneration potions or a beacon. Vanilla hunger and sleep mechanics will not save you.

Concept: One Life, No /tpa, No /home

UHC breaks the moment someone installs EssentialsX and players gain access to /home or /tpa. The whole idea is that you scatter 1500-2500 blocks from spawn, gather resources, craft armor and return to the center as the border shrinks. No teleports, no waypoints, no kit commands.

Additional rules that hold the format together:

• one life per player, on death you go to spectator mode until match end
• healing only via golden apple and potions
• PvP is always on, but the first 20 minutes usually have a grace period with pvp=false
• border shrinks from 2000 down to 50 blocks over 60-90 minutes
• final fight on a tiny arena once the border hits radius 25-50

In short, UHC is a speedrun with a PvP final. Nothing should distract from gathering resources and fighting.

The Vanilla Way Through Gamerule

A minimal UHC can be assembled without any plugins. Log in as operator and run:

/gamerule naturalRegeneration false
/gamerule doImmediateRespawn false
/gamerule keepInventory false
/gamerule announceAdvancements false
/difficulty hard
/worldborder center 0 0
/worldborder set 4000
/worldborder set 100 5400

The last command shrinks the border from 4000 to 100 blocks over 5400 seconds (1h 30m). That is the basic UHC mechanic, and it works on plain Paper or Vanilla without mods.

The catch is that you have to start the timer manually, announce phases, teleport players to spawn, build teams and track who got killed. For a 24-player match the admin loses their mind in the first 15 minutes. That is why people install plugins.

UHC Plugins: What to Pick in 2026

There are plenty of ready-made options for Paper/Spigot, but not all of them are alive. Here is what actually works in 2026:

• UHC Plugin (open source on GitHub) - the basic one, supports teams of 2/3/4, scenarios, border, spectator
• Champions UHC - a fork with extended scenarios, custom items and Discord webhook support
• UltraHardcoreReloaded - a community variant focused on configuration and phase tuning
• CustomUHC - a heavy plugin for tournaments, with leaderboard and stat tracking

If you run a public server with regular matches, pick Champions UHC or CustomUHC. For weekly games with friends, UHC Plugin is enough. All three are written against Paper API and work on 1.20-1.21.

# config.yml for a typical UHC plugin
match:
  duration: 5400              # 1.5 hours in seconds
  border-start: 2000          # initial radius
  border-end: 25              # final radius
  border-shrink-start: 1800   # border starts shrinking at 30 min
  pvp-enabled-after: 1200     # PvP turns on at 20 min
  grace-period: true

teams:
  size: 3                     # solo/duo/3s/4s
  friendly-fire: false
  glow-after-shrink: true     # glow through walls in the final

scenarios:
  cutclean: true              # ore smelts on the spot
  timber: true                # full tree falls when you cut the bottom
  bowless: false
  diamondless: false

regen:
  natural: false
  golden-apple: true
  potions: true

Scenarios: What They Do and Why

UHC is rarely played in a "vanilla" form. Most matches use scenarios, rule modifications that speed up pacing or change tactics. The standard set for competitive UHC:

• Cutclean - ore smelts the moment you mine it, raw meat drops cooked. Without this, 30 minutes go into building furnaces and waiting on smelting
• Timber - chop the bottom block of a tree and the whole thing falls. Saves around 10 minutes on wood gathering
• Bowless - bows are banned or removed from loot. Forces close combat
• Diamondless - diamonds do not drop, but iron armor gets buffed. Levels lucky and unlucky players
• Rodless - fishing rods cannot be crafted or drop a random block
• NoClean - you cannot pick up items for 10 seconds after killing a player

Cutclean and Timber are almost always on. Bowless and Diamondless are tournament-specific. The combo Cutclean + Timber + NoClean is the gold standard for public matches.

Commands for Admins and Players

A basic UHC plugin command set looks roughly like this:

/uhc start                    # start the match
/uhc stop                     # emergency stop
/uhc reload                   # reload config
/uhc team create <name>       # create a team
/uhc team join <player>       # add a player to team
/uhc team list                # show team list
/uhc spectate <player>        # go into spectator
/uhc revive <player>          # revive a player (lag, force-majeure)
/uhc scenario list            # list scenarios
/uhc scenario toggle cutclean # toggle a scenario
/uhc border 100               # manual border change

/uhc revive is rarely needed but critical. If a player dies due to server lag or a disconnect at the wrong moment, you need a way to bring them back. Without it the community will start arguing on the very first desync death.

Players usually get a tiny set: /uhc team list, /uhc spectate, /msg. No /tpa, /home, /sethome, /back - those would kill the format in a single match.

World Pre-generation: Mandatory

If players in UHC scatter 2000 blocks out and the server starts generating chunks live, TPS drops to 12 within 5 minutes. Pre-generation is non-negotiable.

Install Chunky or WorldBorderAPI and pre-generate the entire UHC world ahead of time:

# In server console
chunky world world
chunky center 0 0
chunky radius 2000
chunky start

On an SSD-backed server with 16 GB RAM, generating a 2000-radius world takes 30-60 minutes. Do it once before a series of matches and just reset the world via /uhc reset (the plugin will pick up a fresh copy of the pre-generated map).

If you play regularly, keep 3-5 prepared seeds in a separate folder and rotate between them. A fresh seed per match is the best way to prevent metagaming like "I know where the stronghold is on this seed".

Anticheat: UHC Breaks Without It

UHC is a PvP format, and if you skip anticheat, the first cheater with killaura or reach 4 takes the win. The live options in 2026:

• GrimAC - free, accurate, holds any keep-alive check, works great on 1.20-1.21
• Vulcan - paid, slightly easier to configure, decent PvP presets out of the box
• Polar - newer, but actively developed

For UHC, take GrimAC. It can distinguish legit combo scripts from real killaura, handles knockback correctly and does not bulk-flag high-ping players. Installation is standard: drop into plugins/, restart, you get sane defaults.

# basic GrimAC tuning for UHC
api-key: ""
max-ping: 250
combat:
  reach:
    threshold: 3.1
    max-violations: 4
movement:
  flight:
    threshold: 0.2
  speed:
    enabled: true
  knockback:
    threshold: 0.05

Without anticheat UHC becomes a casino. With GrimAC standard cheats get caught around 95% of the time within the first 10 seconds of use.

Spectator Mode and Streaming

When a player dies, the plugin moves them to spectator. From here you have two options: either silence them in main chat, or move them to a separate spectator channel entirely. The second option is better, since dead players can see through walls and might leak coordinates accidentally (or on purpose).

Standard streaming setup:

• spectator mode for all dead players
• separate chat channel /sc <message> (spectator chat) via DiscordSRV or ChatControl
• 90 second delay on the streamer's OBS so opponents cannot scout positions through the broadcast
• live leaderboard via PlaceholderAPI + a plugin like UHCStats

For tournament streams, run the spectator camera not from a player's perspective, but from a dedicated referee account in /gamemode spectator. That way viewers see the full map state instead of whatever the first dead player happens to be looking at.

FAQ

How long does a UHC match last

Standard length is 60-90 minutes. Tournament formats can stretch to 2 hours, but for public lobbies 75 minutes is the sweet spot. Under 60 minutes is not enough to gear up to full armor, over 2 hours starts burning out players and viewers.

Can you play UHC solo

Technically yes. Install the plugin, set team-size: 1, border 1500, duration 45 minutes. One player against bots or against the timer. But classic UHC is competitive, and solo loses half the appeal. Get at least 4 people if you can.

How do you configure border shrink

Through /worldborder set <size> <time>. For example /worldborder set 50 3600 shrinks the border to 50 blocks over an hour. UHC plugins handle this automatically from config, but if you do it manually, the math is: start at 2000, after 30 minutes shrink to 100 over 1 hour, then to 25 over 15 minutes. The tiny final ring forces players to meet.

UHC vs Hardcore are different formats

Yes. Hardcore is the Minecraft mode with one life, no timer, no border. UHC is a short match with one life, no natural regen and a shrinking border. In Hardcore you can play in one world for months, in UHC the match ends in 1-2 hours and the world resets.

Why disable natural regeneration

That is the entire point of the mode. With regen on, players just hide in a hole for 30 seconds and recover full health after every fight. Disabling it makes every hit count: take 6 damage, lose 6 hearts until end of match or until you eat a golden apple. PvP becomes decisive instead of positional.

Can you run UHC on a vanilla server

You can, but it is painful. Vanilla supports gamerule and worldborder, but not commands, dead-player chat hiding, scenarios, leaderboards or automatic match resets. For a one-off game with friends, vanilla is fine, for regular matches install a plugin.

What Next

If you are launching UHC for the first time, start with a local 4-player test. Verify that the border shrinks, regen is off, golden apples heal, spectator chat works separately. Only then open public slots.

Once the server goes public, set up DDoS protection. UHC servers attract attacks from salty players the moment they die, and a 100 Mbps ICMP flood will take your Paper down in under a minute. MineGuard sits transparently in front of the server and filters attacks at the network layer without touching game traffic.

Third step: automation. Schedule /uhc start every 2 hours, hook a Discord webhook into match start and finish events, rotate pre-generated worlds. After a month you have a working public UHC server with a predictable match calendar.