UPDATING
Every update
- Read the changelog for the new version (Changelog, or the version's page on Modrinth). It says what changed, including any setting whose default moved.
- Stop the server and back up the world and
config/soulverse/together. - Swap the jar in
mods/for the new one. Remove the old one, don't leave both. - Update Strapped too if the changelog asks for a newer one.
- Update every player's game to exactly the same version. If you hand out a modpack, update the pack and tell people.
- Start the server and check the console for errors, then join and open
/sv.
Settings carry over
soulverse-server.json keeps your settings across versions. Every setting is written into the file, so when Soulverse changes a default, an old file would never notice. To fix that the file has a version number: when a newer Soulverse reads an older file, the settings whose default changed since are set to the new default, once.
That's what you want most of the time. But if you had set one of those on purpose, it gets reset, so after an update glance at the settings the changelog mentions.
Player files and logs carry over as they are.
From 0.1.x to 0.3.0
A few bigger changes in 0.3.0:
- The folder moved from
mods/soulverse/toconfig/soulverse/. Soulverse moves it by itself on the first start and never writes over a file that's already in the new place (anything left behind is named in the console). If you have scripts or backups pointing at the old folder, update them. - Strapped must be 0.2.0-beta or newer. Older versions are refused at startup. The back, waist and quiver slots now live in Strapped's own screen rather than Soulverse's inventory. Gear in the old version's slots doesn't come across, so get players to take it out of those slots before you update.
- Settings Presets are new, as is the Restart required line and the presets permission
soulverse.server.presets(ops have it). - New Gameplay switches (No Elytra and the End's dragon settings) are off by default, so nothing changes until you turn them on.
Game version updates
When Minecraft itself updates, wait for a Soulverse build for the new version before moving your server. Each file on Modrinth says which game version it's for; the version number ends in +mc<game version> for the older game versions.
Going back
If an update goes wrong, stop the server, put the old jar back and restore the backup of the world and config/soulverse/ you made in step 2. Running an older Soulverse on files a newer one has already written isn't tested, so use the backup rather than the current files.