Change server startup variables
Use the Startup tab to change a game server’s version, JAR/build, memory and other startup variables safely, and understand when a change triggers a reinstall.
The Startup tab controls how your server launches: the version or build it runs, the main JAR/file, and any egg-specific variables (like which Minecraft server software to download). Changing these is how you upgrade Minecraft versions, switch server type, or tune the boot command — all without touching the command line.
Where to find it
- 1Open the server from your dashboard at control.victuscloud.com.
- 2Click the Startup tab.
- 3You will see the read-only startup command at the top and a set of editable variables below it.
Common variables (Minecraft example)
| Variable | What it controls | Example |
|---|---|---|
| Server JAR file | The file the server launches | server.jar |
| Minecraft / build version | Which game version and build to download on install | 1.21.1 / latest |
| Server type (on some eggs) | Paper, Purpur, Spigot, Fabric, Forge, Vanilla, Velocity, etc. | paper |
| Max memory | Heap given to the JVM (bounded by your plan) | 4096 |
Change a value safely
- 1Stop the server first — do not edit startup variables while it is running.
- 2Take a Backup from the Backups tab (especially before a version change).
- 3Edit the variable(s) on the Startup tab; changes save as you edit.
- 4Start the server and watch the Console — the correct JAR/version downloads on boot if you changed it.
- 5Confirm in the console banner that the expected version/software loaded.
Version jumps can break worlds and plugins
Minecraft worlds usually upgrade forward but rarely downgrade cleanly. Plugins/mods are version-specific — after a major version bump, update them too or the server may crash on start. Always back up first, and test big jumps carefully.
Some changes trigger a reinstall
Switching server type or JAR often makes the server re-download its files on next boot (an install cycle). The server enters the "installing" state briefly — that is expected. Do not interrupt it; wait for it to finish before starting play.
Memory is capped by your plan
You can lower memory in a variable, but you cannot exceed what your plan provides. Setting a max-memory value higher than your allocation will not give you more RAM and may cause the server to fail to start.