Fixing Data and Script Errors in The Hordes and Using Its Commands

This guide explains how to read The Hordes' error messages, list entities, and correct invalid command arguments. Everything here is done through the mod's command interface and its on-screen feedback, so you can diagnose problems without leaving the game.

Reading error messages

The mod reports problems in plain text in chat. Two messages concern loaded content rather than your typing:

• DataError tells you that errors exist in currently loaded data and points you to the file that needs checking.
• DataErrorScripts tells you that errors exist in loaded scripts and names the file to inspect.

When either appears, open the named file and look for the fault it describes. The message will not fix anything on its own — it is a pointer to where the problem lives. Once you have corrected the file, the error should stop appearing.

Correcting invalid arguments

Argument mistakes produce their own messages, and each one names the command it belongs to.

• invalidValue appears when the value you supplied is not acceptable. The message quotes your input and states which argument it was meant for, such as the number of mobs to spawn or the length of the event. Replace that value with one the command accepts.
• wrongArgCount appears when you supply too many or too few arguments. The message names the command involved, so compare what you typed against the command's usage line and add or remove arguments to match.

Every command has a usage string that shows its expected shape. Read it before retrying — it is the quickest way to see exactly what the command wants.

Spawning and starting events

The wave command takes a count: /hordes spawnWave <number of mobs to spawn>. On success you see "Succesfully summoned horde wave". If the count is rejected, you get invalidValue quoting your number; if the argument count is off, you get wrongArgCount for that command.

The event command takes a duration: /hordes start <length of event>. Success reports that the horde event started for the given number of ticks. The same two error messages apply — one for a bad duration value, one for the wrong number of arguments.

Listing entities

Use /hordes listEntities to output a list of all entities. The success message confirms the list was output and tells you where it went. This is useful when you need to confirm what is actually present before adjusting spawn behaviour.

Resetting and clearing data

/hordes reset <optional: player> resets horde data. With a player named, the success message confirms all horde data was reset for that player. The player argument is optional, so the command also works without it.

Separately, a clear action removes all existing horde world data, confirmed by a success message stating that all existing horde world data was cleared. A stop action ends an active horde event for a player and confirms it in chat. A log action outputs the horde log and reports where it was written.

Practical order of operations

When something misbehaves, check for DataError or DataErrorScripts first and repair the named file. Then re-run your command, comparing your input against its usage line. If you still get invalidValue, the value itself is the problem; if you get wrongArgCount, the structure of your input is. Use /hordes listEntities to verify what exists, and the reset or clear actions when you want a clean state.