Die. Learn.
Try again.
Too many deaths in a set time means a temporary ban. Keep hitting the limit and the breaks get longer. Even quick deaths after respawning count.
1h6h24h72h168h
Default ban lengths · change them to fit your group
FREE & OPEN SOURCE · MINECRAFT PLUGIN
Make every
life count.
Hardcore stakes. Another chance.
Give your SMP or friend group a survival challenge. Lose too many lives and take a short break. Play solo or share lives with your team. You pick the rules.
Paper 26.3 Java 25 Alpha
Free to use, change, and share. What open source means for you ↓
THE STAKES, AT A GLANCEIndividual mode
One more chance
isn't a guarantee.
01 First death02 Second death03 Ban triggered
3 deaths in 24 hours1 hour out
Default settings. You choose the rules.
Temporary bansShared team livesFree & open sourceYour server. Your rules.
HOLIDAY BREAK SMP
Ready before
the holiday break.
Christmas, New Year, winter or summer holidays: wherever you are, the break is when friends, cousins and siblings finally play together. Set the rules once and let every life count.
Match your server version
DeathBan Pro 2.0.0-alpha.1 needs Paper 26.3 and Java 25. On Java 21 or Minecraft 1.21, use v1.3.0-alpha.2. Both are alpha builds, so back up your world and try it on a copy first.
Pick a mode for your group
The default is individual: 3 deaths in 24 hours means a ban. For a team challenge, set
mode: shared. The pool starts with 10 lives, and when it is empty each death means a 1-hour ban.Set up teams
Run
/deathban team create <name>and/deathban team join <name>to give each team its own pool. These needdeathban.team.manage, which only operators have by default.Fit bans to a short break
Repeat bans grow from 1 hour to 168 hours by default. Shorten
ban-durationsinconfig.ymlso nobody sits out half the holiday, then run/deathban reload.Keep the peace
By default, deaths in
world_lobbydo not count. If someone is banned right before the group logs on, an admin can run/deathban pardon <player>.
MORE TENSION. MORE TEAMWORK.
Give survival a reason.
For an SMP with real stakes, a team challenge, or your next seasonal event. Start with the defaults and make it your own.
Die. Learn.
Share lives.
Share the stakes.
Switch to shared mode for a server-wide pool or separate team pools. When a pool runs out, further deaths trigger temporary bans.
Server and team pools
Your community.
Your rulebook.
Choose how many deaths are allowed, how long bans last, and which worlds count. Change player messages or give your event a Halloween theme.
Edit config.yml and messages.yml · reload in game or from the console
Know why
someone was banned.
Look up a player's recent bans, expired bans, pardons, and resets. See the reason and ban length when a player asks what happened.
Keeps the latest 100 events per player
Keep lives
in view.
Already use PlaceholderAPI? Show remaining lives, time left on a ban, or team lives in compatible scoreboards and menus.
Optional · requires PlaceholderAPI and a compatible display plugin
FROM DOWNLOAD TO FIRST LIFE
Your next session
starts here.
Bring DeathBan Pro to a Paper 26.3 server running Java 25. Servers on Java 21 or Minecraft 1.21 can use v1.3.0-alpha.2.
Browse releasesChoose a download
Check GitHub Releases for a plugin file ending in
.jar. The latest isDeathBanPro-2.0.0-alpha.1.jar. This project is in alpha, so try it on a test server first. New features on GitHub may arrive before a downloadable release.Install and restart
Place the JAR in your server's
plugins/folder, then restart the server.Set your rules
Open
plugins/DeathBanPro/config.ymlto change the settings. Save, then run/deathban reloadin game or from your server console.
KEEP THE GAME MOVING
Simple commands.
Clear control.
Players can check their status and shared lives. Admins can pardon, reset, and tune the experience.
All commands & permissions/deathban check- Check your ban status
/deathban lives- See how many shared lives are left
/deathban history <player> [page]- See recent bans and admin actions · admin only · page is optional
/deathban pardon <player>- Let a banned player back in · admin only
/deathban reload- Apply saved settings · admin only
BEFORE YOU START
Good to know.
Which version do I need?
DeathBan Pro 2.0.0-alpha.1 needs Paper 26.3 and Java 25. Minecraft 26.4 is not supported yet. Servers on Java 21 or Minecraft 1.21 should use v1.3.0-alpha.2. On Java 21, the 2.0 plugin logs that it needs Java 25 and disables itself.
Does this permanently ban players?
No. Players can come back when their timer ends. You choose how long bans last. Admins can also use the pardon command to let someone back in early.
Can I show lives on my scoreboard?
Yes, with PlaceholderAPI and a scoreboard or menu plugin that supports it. Use %deathban_remaining_lives% for individual lives, %deathban_pool_lives% for shared lives, or %deathban_ban_remaining% for time left on a ban. See the docs for the full list. DeathBan Pro works without PlaceholderAPI too.
Can I protect a lobby or creative world?
Yes. Configure enabled-worlds and disabled-worlds to control where deaths count. The default configuration excludes world_lobby.
What about admins and player permissions?
The default deathban.bypass permission is granted to operators. Admin commands use deathban.admin. Review the permission defaults before testing or opening your server to players.
Where can I get help or report a problem?
Start with the troubleshooting guide, or open an issue on GitHub with your server version and relevant logs.
FOSS: FREE AND OPEN SOURCE SOFTWARE
“Pro” is the name.
Free is the deal.
No paid tier. The plugin's code is public, and the MIT license lets you use it, change it, and share your version. Keep the license and copyright notice with copies.
You don't need to code to take part. Report a bug, suggest a rule for your next SMP, or share what worked for your server.
RAISE THE STAKES
A little less reckless.
A lot more survival.
Browse downloads Free and open source. MIT licensed. Your server, your rules.