Skip to main content

Troubleshooting

Start with these two commands; most problems show up in one of them:

/machineengine status
/machineengine report

status counts the startup problems; report lists them, with the file and place in the YAML for anything from a definitions file.

MachineEngine does not load​

  • CraftEngine is required but is not enabled — CraftEngine is missing or failed to start. Fix CraftEngine first; its own error is earlier in the log.
  • Nothing at all in the log — check the Java version (21 for 1.20.6, 25 for 26.x) and that the server is Paper or Folia, not Spigot.

Machines look like other blocks, or menus show boxes​

Players do not have the current resource pack. Run /ce reload all after installing or updating an addon, and make CraftEngine send the pack as required.

A block does nothing when right-clicked​

  • No zMenu: the log says zMenu is not installed: machines have no menus.
  • No permission: players need machineengine.use.
  • No machine behind the block: the log has CraftEngine block <id> refers to machine type <key>, which is not registered. The block's machine: key is wrong, or the addon or definition that registers that machine failed — see /machineengine report.

A machine does not work​

Look at it and run /machineengine inspect, or turn on /machineengine debug:

  • blocked (orange): its output is full, or something it needs is missing. Empty the output.
  • waiting (aqua): it needs input.
  • red dot: it has an error; inspect shows it.
  • magenta dot: a placeholder — its addon is not installed.

A process that cannot pay its per-tick cost (energy) pauses with the status waiting_for_cost and resumes when the cost can be paid.

A YAML definition is ignored​

Invalid entries are skipped, not fatal: each is listed in /machineengine report with its file and path. Recipes reload with /machineengine reload recipes; new machines and resources need a restart.

"This chunk already holds N machines"​

The chunk reached limits.max-machines-per-chunk (256 by default). Raise it in config.yml, or set 0 for no limit.

Players are refused on join with "Your data could not be loaded"​

Their player data did not load within players.load-timeout seconds (only with a storage other than machineengine:pdc). Check the log for the storage's error; with machineengine:files, a damaged file is moved aside as .damaged-<time>.

Still stuck​

Open an issue with the server version, the MachineEngine and CraftEngine versions, the output of /machineengine status and report, and the log.