Freeze the exact stack
Write down the game version, loader, loader version, pack release, Java version, and required client files. A small version mismatch can stop the server or block players from joining.
- Keep a pack manifest
- Save the original configuration
- Name the update owner
- Document every client requirement
Plan the world and activity
An established world, new chunk generation, machines, entities, and automation can change the workload. Record your expected peak activity and import size before you ask for plan guidance.
Protect every change
Create a backup before you update the game, loader, mods, or configuration. Test the restore path before you rely on that backup.
- Change one layer at a time
- Keep rollback notes
- Test server and clients together
- Remove failed changes cleanly
Check what we have proved
We will base the future support matrix on repeatable install, startup, workload, backup, restore, update, and rollback checks on the real node.
Read the version validation method