Stop, Backup, Edit, Start: Safe Game Server Changes

The MSP habit that saves worlds

Most broken worlds and “it won’t boot” nights start the same way: someone edits a config or drops a mod while the process is still writing saves. GlassHosting treats file changes as a planned cutover—not a live tweak on a box friends are still playing on.

The sequence is short on purpose: quiet window → Stop cleanly → named Backup → edit → Start → smoke-test join. It is the same for Minecraft, Valheim, Enshrouded, BeamMP, Vintage Story, Windrose, Palworld, Rust, Hytale, and every other Glass Gaming title on the panel.

New to the panel? Skim the game panel beginner guide first. Need File Manager vs SFTP detail? Use Panel File Manager and SFTP for Game Servers.

1. Pick a quiet window

Tell the group before you touch files. A five-minute heads-up beats a mid-raid disconnect.

Ask players to log out (or wait until the session is naturally quiet).
Skip peak play nights when you can. Config and mod experiments belong in a window you control.
If someone must stay online for a moment, they still need to leave before you Stop—open worlds keep writing.

2. Stop cleanly

Open the game service in panel.glasshosting.com.
Click Stop.
Watch the console until the process shows a clean shutdown—not a forced kill mid-save.

Do not open File Manager or SFTP while the console still looks “running.” If Stop never reaches a stopped state, do not yank world folders. Ticket support before you force-overwrite a live save directory.

3. Named Backup first (non-negotiable)

Before any experiment that touches configs, mods, plugins, or worlds:

Create a named panel backup so you can restore by label, not by guesswork.
Or download the critical folders via File Manager / SFTP to your workstation as a second copy.

“There was probably an auto backup” is not a restore plan. The habit is the same across titles—see backups before mods.

4. Edit via File Manager or SFTP

Stay inside the service root the panel shows. Match the folder layout that title expects.

Panel File Manager — best for a few small files: tweak a .json / .cfg / .properties, rename a folder, delete a bad upload.
SFTP — best for bulk uploads: mod packs, plugin jars, map packs, large world directories. Use FileZilla, WinSCP, Cyberduck, or any standard SFTP client against the credentials the panel shows for that service.

Rule of thumb: handful of kilobytes → File Manager. Whole content pack or world tree → SFTP. Full walkthrough: Panel File Manager and SFTP.

When you replace a world or save folder, prefer rename-old → upload-new over deleting the live save first, so you still have the previous folder on disk if the transfer fails.

5. Start once, then smoke-test

Confirm File Manager / SFTP sessions are idle and transfers finished.
Click Start in the panel.
Watch the console until the process reports ready—or until an obvious config/mod/plugin error appears.
Fix errors before inviting the group. Do not rapid-restart in a loop that interrupts saves.
Have one trusted friend join with the panel IP and port (see how friends join with IP:port), confirm the world and content look right, then announce to everyone.

If boot fails after a file change: Stop, restore the named backup (or rename the previous world folder back), Start once, and verify a clean console before trying the experiment again.

When to open a ticket instead

Stop never reaches a clean stopped state and you need to protect a live world.
Restore from a named backup still will not boot, and the console error is unclear.
You need a change that is outside normal file ops (allocation, network, or account-level help).

Use billing support from billing.glasshosting.com, and skim the billing knowledgebase for deeper how-tos already published. Include what you changed, the named backup label, and the console lines that failed—not a vague “it broke.”

Quick checklist

Quiet window agreed; players out
Server Stopped cleanly (console confirms)
Named backup (or downloaded copy) exists
Edit done in the correct folders via File Manager or SFTP
Transfers finished before Start
Start → console clean → one-friend join smoke-test
Ticket only when Stop/restore/network is beyond self-serve

Related guides

MSP note

GlassHosting runs game changes the same way we run store cutovers: stop, backup, change, start, smoke-test—not live edits on a session friends are still in. Order or manage plans at billing.glasshosting.com; operate day-to-day at panel.glasshosting.com. Glass Gaming — powered by GlassHosting.