Updating & downgrading
- Back up the server (worlds included: machines are saved in them).
- Stop the server. Do not use
/reloador a plugin manager to swap the jar. - Replace the MachineEngine jar in
plugins/, and update its addons at the same time if they ask for the new version. - Start the server, then check
/machineengine status.
What an update does to your files
| File | On update |
|---|---|
config.yml | New settings are added with their defaults and comments. Your values and comments stay. |
menus/machine.yml | Written only if missing: your edits stay. Delete it to get the new default. |
menus/player_settings.yml | Rewritten at every start, until you delete its first line to keep your own version. |
definitions/example.yml | Written only when the definitions/ folder does not exist. |
CraftEngine/…/machineengine/lang.yml | Never overwritten. Delete it to get new keys and languages. |
CraftEngine/…/machineengine/templates.yml | Rewritten at every start: it must match the running version. Do not edit it. |
Removing an addon
Machines of an addon that is no longer installed are kept as placeholders:
they stop working but keep all their data, and come back when the addon is
installed again. Players cannot break them (unless placeholders.allow-breaking
is on, or they have machineengine.admin.breakplaceholders, which operators
have by default), since breaking one destroys its data.
/machineengine placeholders list shows the loaded placeholders;
/machineengine placeholders purge deletes the data of one for good. See
Commands.
Downgrading
Downgrading is not tested. Restore the backup you made before updating rather than running an older jar on newer data.