Configuration updates
Navigation: Updates — route /config-updates
OpenMU is under active development, and new versions regularly bring changes to the game configuration data: a corrected monster stat, a new drop item group, a new plugin configuration, a fixed quest.
Your database keeps the configuration you initialized (and possibly customized), so those changes cannot simply be applied by updating the software. Instead they come as configuration updates, which you apply here.
The navigation menu shows a badge with the number of available updates, so you notice them after an upgrade.
Applying updates
The page lists every update which has not been applied to your database yet, with its description.
- Mandatory updates are always applied and cannot be deselected — the server requires them.
- Optional updates can be selected or deselected individually, which lets you keep your own customizations where an update would overwrite them.
After the run, each update is marked as applied or, when something went wrong, as failed.
The updates take effect after a restart of the server process. Until then, the running server still works with the configuration it loaded at startup.
Preconditions
If the database is not installed yet, or a schema update is pending, this page refers you to the Setup page first — configuration updates are applied on top of a current schema.
Good practice
- Take a backup of your PostgreSQL database before applying updates to a server which has players on it.
- Read the descriptions. If an update touches something you customized (drop rates, monster stats), you may want to deselect it and merge the change yourself in the game configuration.
- Apply updates during a maintenance window, since a restart is needed anyway.