Server Console
Eranio
Server Console and Installing Updates
Hint tile
As soon as an update is detected for a server, a tile appears above the player console with the installed and the latest version. For Hytale sources with an expired downloader login, the tile shows a dedicated hint about that instead. If a newer Minecraft version is also available, that is added to the tile.
Installing an update
Clicking the tile opens a confirmation showing the installed and the new version. The confirmation states that a native Pelican backup runs first, the update only starts afterwards. The backup is automatically named "Update Checker" with the date and the old and new version.
If the server has no free backup slot left, the toggle "Update without a backup" also appears. It is off by default and shows a clear warning that a change without a backup cannot be undone if something goes wrong. Existing backups are never deleted to make room.
While the update runs, the tile turns into a step by step display, backup, set variable, apply update, done, polling every two seconds, with a clear final state, done or failed, and a close link. Several servers can be updated at the same time without blocking each other.
When the update ends in a reinstall, the toggle "Start automatically afterwards" also appears, on by default. If the server was running before, it is started again automatically after a successful reinstall, if it was stopped before, it stays stopped. A failed reinstall is reported clearly and never starts the server.
Switching the Minecraft version
If the current build is already the newest one, but a newer Minecraft version already exists on Purpur, Paper or Leaf, the tile also offers switching to it, even while a regular build update is available at the same time. The confirmation warns clearly, the world is converted on the first start on the new version, after that only the backup leads back to the old version, and plugins as well as Geyser or ViaVersion, if used, need to already support the new version. The switch sets the Minecraft version and the build number and reinstalls the server.
Success check after the update
After every applied update the plugin automatically rechecks for up to three minutes whether the installed version really changed. This is needed because Steam and the other readers only write their version file once the process is truly finished, an immediate look would often still show the old version. Once the new version is confirmed, the tile shows "Done". If it stays unchanged, the tile shows "Update failed" with the detected reason, see also the "Troubleshooting" page.
Steam self heal
If Steam reports "Access Denied" or "Failed downloading" in its own log during the success check, the plugin automatically attempts a repair: the existing appmanifest file is renamed once, so Steam no longer treats the folder as already fully installed on the next attempt, then a single further restart runs. Once the new version is confirmed afterwards, the renamed file is removed again. If a server has several log files, the newest one always counts for this check. If this further restart runs through Steam for an automatically detected source without the version actually changing, the plugin switches the source to reinstall for the next attempt on its own. For a source maintained by hand this never happens automatically, only a log hint appears there.
How a reinstall is avoided
For source types with an automatic update method, Purpur, Paper, Leaf, Hytale, Forge and update only, the install script of the egg is checked before every reinstall, using the actual variable values of that specific server rather than only the egg in general. If it deletes directories with user content without a guard, mods, libraries, plugins, world, config and similar, the reinstall automatically becomes a restart instead. A deletion behind a condition only counts as safe when it can be proven for this one server that the condition does not apply, an unknown variable, a file test or a path containing a variable always count as not safe. A restart never changes anything on the server files. The plugin also compares a list of the usual mod, plugin, world and config folders before and after a reinstall, the reasoning is shown on the confirmation screen before the reinstall.
Permissions for subusers
Root admins can always apply an update. For other users of a server, depending on the method:
- always: create backup
- when a variable is set: edit startup variables
- when the method is restart: restart the server
- when the method is reinstall: reinstall the server, plus start the server