Make a BedWars plugin that matches your own server setup

Why an off-the-shelf BedWars plugin never quite fits

A public BedWars plugin was written for someone else's server. Its author already decided how many teams there are, how fast the generators tick, what the shop sells, how long spawn protection lasts, and how a bed break gets announced. What you get is a config folder where you try to twist those decisions into yours.

The limit is not the size of the config file, it is what the config file never exposes. The day you want a fifth generator tier, a solo team mixed in with squads of four, or a shop whose stock changes halfway through the round, you hit a wall: that behaviour is not in the code, so no option is going to summon it.

A generated plugin works from the other end. You write the rule, the rule becomes code. If your mode has an idea nobody has published yet, it sits in the brief next to everything else instead of being impossible.

What you get to decide in your own BedWars

The more specific your description, the closer the plugin lands to the mode in your head. These are the parts where a BedWars round is actually won or lost, so spell them out before you generate.

• Format: how many teams, how many players per team, and what happens when the queue is not full
• Beds: one bed per team or several, protection around the bed, what players see when a bed drops
• Respawn: instant or on a countdown, where the player reappears, and with what starting kit
• Elimination: a bedless player becomes a spectator, and a wiped team ends the round
• Generators: which resources, where they sit, how fast they tick, how tiers escalate
• Shop: where it opens, what it stocks, and what each item costs
• Endgame: win condition, rewards, return to lobby, arena reset between rounds
• Commands and permissions: who starts a round, who joins, who can force-stop it

Generators: the setting that sets the pace of every round

Generator speed is the real difficulty dial in BedWars. Fast resources make short, violent rounds where the opening rush decides everything. Slow resources make long rounds with thick defences and players meeting in the middle of the map over diamonds.

So describe the feel you want, not just the mechanic: team resources ticking at each base, rare resources placed in contested ground, and optionally tiers that speed production up as the round goes on to force a fight when nobody wants to move first.

Then cover the small things that get annoying in game if you skip them: whether uncollected drops pile up on the floor, whether each generator has a cap, and whether a chat message announces the next tier.

• Which resources spawn at each team base
• Which resources sit in shared, contested areas
• How the tick rate changes over the course of a round
• What players are told when a tier upgrades
• What happens to items nobody picks up

Shop, currency and kits: your in-round economy

The shop is where your BedWars becomes recognisable. Two servers with identical generators but different shops do not play alike at all. Write out your categories, your items and their prices, and remember that every price is a gameplay decision: defence blocks priced too high push everyone into rushing, a cheap weapon kills the long game.

That in-round currency is internal to the minigame and has nothing to do with your server-wide economy. If you do want the two connected, for instance a payout credited to the winners afterwards, say so in your description and name Vault or whichever economy plugin you already run.

Same for ranks: if you use LuckPerms to reserve a queue or a cosmetic for supporters, mention it, and the code will be written with that in mind.

• Shop categories and what sits in each one
• The price of every item in the in-round currency
• Team upgrades, if you want them, and exactly what they do
• The kit a player gets back on every respawn
• Any link to your server economy or rank plugin

How to describe your BedWars so the plugin comes out right

Write it the way you would explain your mode to a friend who has never played on your server: one full round, start to finish, assuming nothing. Open with the format and the map, move through generators, shop and beds, and finish with the win condition and the arena reset.

Name your commands exactly as you want them typed, say who is allowed to use each one, and write out the chat messages your players should see. Name your Minecraft version and your platform too, Paper, Spigot, Bukkit or Folia, so the code is written against the right API.

Minax generates the Java code, compiles it to a .jar, and runs a self-correction loop over compile errors before handing you the file. If the result is not quite your mode yet, add a sentence and generate again. For an ambitious minigame that usually beats trying to specify everything in one go.

• Walk through a complete round in chronological order
• Give exact command names and the permissions behind them
• Write the chat messages you want players to read
• State your Minecraft version and your server platform
• Build in passes: the core mode first, the extras after

Play a round before you open it to your players

A minigame is not judged on its source, it is judged on a round. That is why the generated .jar can be launched online on a real Paper server: you join, type your commands, break a bed, and watch whether the chat and the respawn behave the way you wrote them.

Look first at the things that ruin a round in front of an audience: a team stuck in the lobby, a generator that never starts, a shop that takes payment without handing over the item, an arena that does not reset between rounds. Check those before you announce the mode in your Discord.

Once a round plays cleanly, download the .jar, drop it in your server /plugins folder and restart. The source code is yours: read it, tweak a value by hand, or send your description back for another pass.

Frequently asked questions