Routine restart and update
- Announce a restart, save the world from the server console when possible, and create a backup.
- Stop through the panel and wait for the process to exit. Make the planned change, then start and watch for the map-loading and ready messages.
- After a game update, verify a current client can connect before deleting the backup.
Oxide or Carbon plugins
- Confirm the service is running a Runic-supported Rust loader. A vanilla Rust install will not load Oxide or Carbon plugins.
- Back up first and use only a framework build compatible with the current Rust server release. Install one vetted plugin at a time in the loader’s plugin directory.
- Restart and check the loader log for compilation or permission errors. Rust updates can overwrite Oxide and require a matching framework update.
ImportantRunic does not present an unvalidated plugin framework as automatic one-click installation.
Not visible or cannot connect
- Use the assigned game address for a direct connection while server-list indexing catches up.
- Check the console for a completed startup and confirm the configured game and query ports have not been changed away from the assigned values.
- If a custom map fails to download, verify its direct-download URL and inspect the client/server error before replacing the map.
Crash or unexpected wipe
Check server identity, seed and world size against the last working values. Changing seed or size can generate a different map. Restore the matching save and configuration together from the backup; do not delete live save files while investigating.