The Hordes Mod: Using /hordes Commands to Spawn Waves and Start Events

guide

The /hordes command is the main way to control horde activity in The Hordes, covering wave spawning, event timing, data resets, and diagnostics. Every subcommand runs from chat, and each one reports back with a short status message so you know whether it worked.

Spawning a Wave

Use /hordes spawnWave <number of mobs to spawn> to summon a horde wave. Replace the placeholder with the count of mobs you want. On success the game confirms with a message that the horde wave was summoned.

If the count you typed can't be read as a number, you get an error naming your input and stating it is not a valid argument for the mob count. If you supply the wrong number of arguments, a separate error tells you the argument count for the wave command is incorrect. Fix the count or the argument list and run it again.

Starting an Event

Use /hordes start <length of event> to begin a horde event, where the argument is how long the event lasts measured in ticks. A successful start confirms the event began and repeats the tick length you gave.

The same two failure modes apply: an unreadable length produces an error naming your input as invalid for the event length, and a missing or extra argument produces an argument-count error for the start command.

Stopping Events and Other Actions

Beyond spawning and starting, the command handles several housekeeping actions, each with its own confirmation message:

Stopping an active horde event reports which player the event was stopped for.
Outputting the horde log reports the destination it was written to.
Clearing all existing horde world data confirms the wipe.
/hordes reset <optional: player> resets horde data; the player is optional. The confirmation names the player whose data was reset.
/hordes listEntities outputs a list of all entities and reports where the list was sent.
/hordes spawnZombie is available as its own subcommand for spawning a zombie.

Reading Error Messages

Two error types point at problems with your loaded content rather than your typing:

A data error tells you that errors exist in currently loaded data and points you to the file to check.
A scripts error tells you that errors exist in loaded scripts and points you to the relevant file.

When either appears, open the named file, correct the problem, and reload before expecting commands to behave normally.

Quick Reference

/hordes spawnWave <number of mobs to spawn> — summon a wave.
/hordes start <length of event> — begin an event for a tick duration.
/hordes reset <optional: player> — reset horde data, optionally for one player.
/hordes listEntities — output all entities to a destination.
/hordes spawnZombie — spawn a zombie.

Type the subcommand exactly as shown and match the argument type each one expects: a number for waves, a tick length for events. Most failures come down to a non-numeric value or the wrong count of arguments, and the error text tells you which of the two occurred.