Game server tutorials6 min read
Backups that actually work when you need them
A backup you have never restored is a hypothesis. How to set up game server backups you can genuinely rely on, and the mistakes that make them useless.
The first modded server most people run goes the same way: it works, everyone is delighted, and then a week later it is a fragile pile of version mismatches nobody wants to touch. The mods are not the problem. The problem is that a modded server has different rules from a vanilla one, and nobody mentions them up front.
Mods and plugins are not the same thing
This distinction causes more confusion than anything else in modded hosting.
- Plugins (Bukkit, Spigot, Paper for Minecraft) run server-side only. Players connect with an unmodified client. Great for gameplay rules, permissions and admin tooling.
- Mods (Forge, Fabric, NeoForge for Minecraft; BepInEx for Valheim) usually change game content and need matching versions on both the client and the server.
If you want new blocks, machines, dimensions or creatures, you need mods and every player needs the same pack. If you want permissions, land claims, economy or moderation tools, plugins are simpler and your players install nothing.
Version pinning is the whole game
Write down three things and treat them as one unit: the game version, the mod loader version, and the pack version. Change any one of them and you have a new configuration to test.
Do not let players update their pack independently. "It updated itself" is the single most common cause of a modded server everyone is suddenly unable to join.
The practical fix is to distribute a specific pack version through a launcher your players all use, and to announce updates deliberately rather than letting them drift.
Memory and startup time both go up
A vanilla Minecraft server for a few friends is fine on 2 GB. A large modpack starts at 8 GB and is more comfortable at 12 to 16 GB. Startup goes from a few seconds to several minutes, because every mod registers its content before the world loads.
This matters for how you operate the server. A five-minute startup means a careless restart during peak hours is genuinely disruptive, so schedule restarts for quiet periods and warn players first.
Read the crash log — it is more helpful than you expect
Modded crash reports look intimidating but usually name the culprit within the first twenty lines. Look for the mod ID in the stack trace and the "Suspected Mods" section if the loader provides one.
- Missing dependency — a mod needs a library mod you did not install.
- Version mismatch — a mod built for a different game or loader version.
- Mixin conflict — two mods patching the same code. Usually needs one of them removed.
- Out of memory — the pack needs more than you allocated.
Back up before every change
Modded worlds are fragile in one specific way: removing a mod that added blocks or items leaves holes in your world data. Sometimes that is harmless, sometimes it corrupts chunks. Always take a backup before adding or removing a mod, and always test a pack update before rolling it out to players.
Adding and removing mods safely
- Take a backup and confirm it downloaded successfully.
- Stop the server properly rather than killing it.
- Make one change, not five.
- Start the server and watch the console until the world finishes loading.
- Join and check the affected area before announcing anything.
- Only then distribute the updated pack to players.
