← Minecraft guides

Minecraft · updated 8 November 2026

A build battle on your Minecraft server, no plugins

A build battle can be run without plugins: a walled-off plot for each player, a theme, a time limit and a final tour where everyone visits the builds and votes. With the commands in this guide, the server itself counts the votes and shows them on screen.

Different case? Ask with this guide inChatGPTClaude

How a game works

Each player has their own plot, closed off with invisible walls so nobody wanders into someone else's. A theme is announced (a ship, a treehouse, a monster) and everyone builds in creative for the agreed time, 15 to 30 minutes. At the end, everyone switches to spectator, the plots are visited one by one and each player rates the others' builds from 1 to 5. Whoever scores the most points wins.

The commands are typed into the panel's “Console” as they are, without the slash. They also work in game, with the slash and as an operator (in “Console”, op and your name). The voting ones can be used by anyone, without being an operator.

Rather not set it up yourself? Minecraft servers from €6 a month, no contract and a full refund within 72 hours. Or create a free Minecraft server, no card needed.

1. The venue: a separate flat world

The easiest is a flat world: nothing needs levelling and the plots sit in a row. If the server is also your survival world, add it as a second world with Multiverse (explained in the multiple worlds guide) so the contest doesn't leave stray builds in yours.

Before you start, make a backup in “Backups”: if something goes wrong, you're back to the world from before in a minute.

2. The rules: creative without surprises

In creative anything goes, including what ruins a contest: TNT, fire eating the neighbour's wood or monsters spawning at night. These rules remove all that and keep it always daytime with no rain. fire_spread_radius_around_player at 0 stops fire jumping to nearby blocks (since 1.21.11 it replaces doFireTick).

If you copy rules from an old video, like doDaylightCycle or doMobSpawning, the server won't recognise them: since 1.21.11 they're lowercase with underscores.

Console: rules (once)
gamerule tnt_explodes false
gamerule fire_spread_radius_around_player 0
gamerule mob_griefing false
gamerule spawn_mobs false
gamerule advance_time false
time set day
gamerule advance_weather false
weather clear
gamerule pvp false

3. The plots: barrier boxes

Each plot is a box of barrier blocks (invisible, but you can't pass through them) 34 × 34 blocks and 21 high, with a white concrete floor. Whoever is inside builds in 32 × 32 and can't fly off or stray into someone else's by accident. Careful: in creative a barrier can be broken on purpose, so the contest rule is not to touch the walls (anyone who does is disqualified).

Build the first one with /fill and copy the rest with /clone, leaving a few blocks between them. Use fixed coordinates: check where you are with F3 and change the numbers in the example (here, the first corner at 0 64 0). Do it in spectator (gamemode spectator and your name) so you don't get boxed in, and stay close: /fill and /clone only work in the loaded area around players.

Don't make the box bigger without doing the maths: /fill and /clone change at most 32 768 blocks at once (the max_block_modifications rule), and this one takes 24 276. For a taller one, raise the rule first or build it in two parts.

Console: the first plot
fill 0 64 0 33 84 33 minecraft:barrier hollow
fill 1 64 1 32 64 32 minecraft:white_concrete
Console: the next ones, 40 blocks apart
clone 0 64 0 33 84 33 40 64 0
clone 0 64 0 33 84 33 80 64 0
clone 0 64 0 33 84 33 120 64 0

4. The round, step by step

Replace Ana with each player's name. The centre of the first plot in the example is 16 65 16; the second's, 56 65 16 (add 40 to the first number for each plot).

  1. Everyone to their plot

    tp Ana 16 65 16, and the same for each player in theirs. Then gamemode creative @a.

  2. The theme

    title @a title "Theme: a ship" and title @a subtitle "30 minutes". So nobody brings something pre-planned, pick the theme on the spot, or have someone who isn't playing draw it at random.

  3. Time warnings

    With 5 minutes and 1 minute left, title @a actionbar "5 minutes left". The organiser keeps time: a kitchen timer will do.

  4. Time's up

    gamemode spectator @a. In spectator nobody can touch another block and everyone passes through the barriers to visit the plots.

5. The votes: 1 to 5, counted by the server

With /trigger any player can set themselves a number without being an operator: we use it to vote. Before the tour, create two scoreboards: vote (what each player gives) and points (what each plot adds up, shown on the side of the screen).

At each plot, everyone except its builder votes by typing /trigger vote set and a number from 1 to 5. After about 30 seconds, the organiser adds the votes to the builder and clears them for the next one. Votes outside 1 to 5 don't count, and builders can't vote for themselves because voting is only enabled for the others.

Console: before the tour (once)
scoreboard objectives add vote trigger "Vote"
scoreboard objectives add points dummy "Points"
scoreboard objectives setdisplay sidebar points
Console: at Ana's plot
tp @a 16 75 16
scoreboard players enable @a[name=!Ana] vote
title @a actionbar "Vote: /trigger vote set 1 to 5"
Console: when closing Ana's vote
execute as @a[name=!Ana,scores={vote=1..5}] run scoreboard players operation Ana points += @s vote
scoreboard players reset @a vote

6. The winner and the next round

At the end of the tour, the sidebar shows everyone's points, highest first. If there's a tie, a quick vote between the tied players only: scoreboard players reset @a points and another visit to those plots.

For the next round, plots are emptied by cloning an empty one over them: keep one unused (for example, 400 blocks away) and clone it over each with the same /clone as in step 3. Or go back to the backup from before the contest. When you're completely done, scoreboard objectives remove vote and scoreboard objectives remove points.

What the server can't stop

In creative, builds can be copied with client mods (schematics) or brought in ready-made. Agree beforehand that everything is built by hand and within the round. As for lag, watch out for thousands of blocks of sand or water at once: the server calculates all of it, and a 32 × 32 plot doesn't need that.

If you want something more polished (random themes, an on-screen timer, voting with items), there are build battle plugins: look for them in the panel's “Mods & plugins” and check they list your version before installing. For an event among friends, the commands above are enough.

With NapNodes

The free server handles a contest among friends: no card, you turn it on with “Start” when you're going to play and it shuts down by itself after an hour with nobody on. If there's a queue to start, turns last 2 hours; for a contest with several rounds, a plan is more relaxed and stays on 24 hours a day. Wood (3 GB) is enough for a group of up to 8 without mods, which is what a contest needs: commands weigh nothing.

The “Theme” and “Time's up” messages look better with colours: the /tellraw and /title generator writes them for you.

Frequently asked questions

Can you do a build battle in Minecraft without plugins?

Yes. Walled-off plots with barrier blocks (/fill … minecraft:barrier hollow), creative to build, spectator to visit and votes with /trigger, which any player can use without being an operator.

How do I make each player build only in their plot?

Lock them in a barrier box: it's invisible and won't let anyone through, not even flying. In creative it can be broken on purpose, so agree that nobody touches the walls. In spectator you pass through it, which is why the final tour is done in that mode.

How do you vote in a Minecraft build contest?

With a trigger scoreboard: scoreboard objectives add vote trigger, scoreboard players enable for those voting, and each one types /trigger vote set and their score. scoreboard players operation adds the scores to the plot's builder.

Why does /fill say there are too many blocks?

Because /fill and /clone change at most 32 768 blocks at once, which is what the max_block_modifications rule sets. Do the area in parts or raise the rule with gamerule max_block_modifications.

How do I stop TNT or fire ruining the builds?

With gamerule tnt_explodes false and gamerule fire_spread_radius_around_player 0. Since 1.21.11 doFireTick no longer exists.

Shall we set it up for you?

Minecraft servers from €6 a month, never oversold: your RAM is yours alone. And if you'd rather start without paying, there's a free Minecraft server, no card needed.

Your server doesn't show up in the game? Check it in a second with “Is my Minecraft server online?”: players, version and MOTD, free. Need a player's UUID for the whitelist or permissions? Look it up here. Handing out enchanted items? Build the command with the /give generator.

Free tool: /tellraw and /title generator. Messages with colours, bold and click actions in chat or across the screen: the /tellraw or /title command ready to copy.

Keep reading

All Minecraft guides, sorted →