Minecraft Command Manager

At a glance

The Command Manager runs server commands for you on a repeating schedule. You pick one from a list, fill in its parameters, choose when it runs, and save.

It sits on the Event Manager page next to Config Events. Config Events change settings and restart the server for a while - a weekend with different rules. The Command Manager sends console commands and restarts nothing.

All five Minecraft flavours share one catalog. Vanilla, Paper, Forge, NeoForge and Fabric get the same 24 commands, because these are the commands the *server* understands rather than anything a mod loader adds. Plugin and mod commands are still reachable through Custom Command.

Your first schedule

1. Open your server, click Event Manager, then the Command Manager tab.

2. Click + New Schedule.

3. Name it Auto Save.

4. Pick Save World from the dropdown.

5. Choose Every N minutes and set 30.

6. Click Create, then Run Now, then Log.

The log row will read "Sent, unconfirmed" - that is correct on Minecraft, and the next section explains why.

The only game that can say "everyone" in one command

Ten of the 24 commands take a player: Display Title, Kick, both Teleports, Give Item, Clear Inventory, Set Gamemode, Give XP, Set XP and Give Potion Effect. Each shows an Send to every online player checkbox beside the player field.

On Minecraft that checkbox does something no other game we host can. @a is part of Minecraft's own command language - it means every player online - so ticking the box substitutes @a and sends one command.

give @a diamond 64

No roster is fetched, nothing is looped over, and the server resolves "everyone" itself at the instant the command lands.

You can of course type @a yourself, or a narrower selector like @a[distance=..100]. The checkbox is there so you do not have to know that.

This is not the `{playerNames}` variable. The checkbox targets everyone. {playerNames} writes the list of names into a message - say Online now: Ada, Bob, Cy. Announcing who is on is the variable; handing everybody a diamond is the checkbox.

The 24 commands

Server

World and time

Blocks - read the warnings on these

Think twice before putting any of those four on a repeat. A fill that was right when you wrote it stays pointed at the same coordinates forever, and a player who builds there afterwards loses the lot on the next run. A hostile mob summoned into somebody's base on a nightly schedule is a support ticket waiting to happen.

Players

Every player command needs its target online when it runs. A command aimed at somebody who has logged off does nothing.

Custom

Custom Command sends exactly what you type. This is where plugin and mod commands go - a Paper plugin's /tps, an Essentials command, anything the catalog does not carry. Nothing checks the syntax first.

Why runs say "Sent, unconfirmed"

Open the log on a Minecraft schedule and most rows will be amber, reading Sent, unconfirmed, rather than green.

That is honest rather than broken.

Minecraft's console is a one-way pipe. A command the server ran perfectly and a command it threw away produce the identical empty response. So a Minecraft step is recorded as "sent" - which is exactly what we know - instead of being given a green tick it cannot earn.

Games with a real reply channel, like 7 Days to Die over telnet or Palworld over its REST API, still show Success with the server's own output underneath.

Questions are different. When the platform needs an answer from Minecraft - reading the player list for {players}, or for a "only when players are online" condition - it asks over RCON, which *does* carry a reply. That is why those work even though ordinary commands come back silent.

The practical consequence: to check a scheduled Minecraft command did what you wanted, look at the game. The log can only tell you it was delivered.

Schedules worth building

That last one works because list is a *question* - its answer comes back over RCON and lands in the history.

A rotating hourly tip

Broadcast Message, hourly, Run this set to "Only when players are online":

Tip: {randList:Build a bed before dark,Bank your loot,Repair your gear at the anvil}

Restart warnings that cannot drift

{nextRun} reads the real next-run time as the message goes out, so it stays right even if the run is a few minutes late. Set Run this to "Only while the server is up".

Reading the history

Click Log for the last 50 runs, each with the exact command sent, any output, and a status.

On games that expand per player, an Send to every online player step gives one row per player. On Minecraft there is one row, because there was one command.

Each status and what to check: Command Manager Troubleshooting.

Everything else a schedule can do

Multi-step sequences, waits, run conditions, overlap policy, catch-up windows, start spread and missed-run alerts work the same on every game.