GM commands and reloads

Chat commands

Commands are typed in the game chat and configured in MuServer/Data/Command.txt: each row defines whether the command is enabled, its cost, the minimum and maximum levels and resets, the delay between uses and the required account level (0 player, 1 Game Master, 2 administrator).

Game Master accounts are managed from the GM Manager in the web panel.

To create a test item, for example: /make <section> <index> (/make 0 32, /make 13 400).

Bringing events forward

Since version 0.97.30, a GM of level 1 or higher can bring an event forward without touching its schedule or restarting the server:

• The event starts once, about two minutes after the command.
• The file schedules are not modified and active events are not restarted.
• Blood Castle and Devil Square reject the request if their entry is already open.
• Starting one invasion does not restart the others.
• The event must be enabled in its configuration.
• Each request and its result are written to the command log.

If you upgraded from an earlier version

A persistent volume does not receive the new Command.txt. Add the four new rows from the repository file to your Data/Command.txt after /tamastart and before end, in this order: /bcstart, /dsstart, /bingostart, /invasionstart.

The row order defines each command’s number: don’t reorder them or insert others in between.

Reloading files without restarting

The Linux server does not read commands from the console: typing shop or /reload shops in the container terminal does nothing. To request a reload, write the name of what you want to reload into the EditorReload.flag file, inside the Data folder. The server reads and consumes it within about 10 seconds.

With the optional editor enabled, the web panel does this for you when you save a file from its editors. By hand, from the folder of your docker-compose.yml:

docker compose exec -T mu-server sh -c 'printf "shop\n" > "${MU_DATA_PATH:-/opt/mu/Data}/EditorReload.flag"'

If you are already inside the container shell:

printf 'shop\n' > "${MU_DATA_PATH:-/opt/mu/Data}/EditorReload.flag"

The server log should show Shop reloaded by editor flag.

• With the published-images compose file, add -f docker-compose.images.yml after docker compose.
• Without Compose, use docker exec <container> instead of docker compose exec -T mu-server.

What can be reloaded

all, common, shop, monster, move or gate, quest, util, item, skill, event, eventitembag, chaosmix, command, custom, character, map and hack.

You can request several at once, separated by spaces or commas. Wait for one request to be consumed before sending another.

event and all reinitialize the events: don’t use them to bring one forward or while an event is running. That is what the commands above are for.

The catalog customs (items, effects and pets) are sent at login: after changing them, restart the server. See Customs.