The startup command#
The startup command is the line your server runs when it boots. Open the Startup Settings page and you will see the current command in two forms. The "Raw Command" is what you wrote, with placeholders like {{SERVER_MEMORY}} still in place. The "Processed Command" below it carries a "Read-only" label and shows the same line with every placeholder swapped for its real value, so you can read the exact command the server will run. Click either block to copy it.
To change the command, click "Edit Command". You get a "Raw Command" box on one side and a "Live Preview" on the other. As you type, the preview resolves your placeholders in real time, so you can confirm a change reads correctly before you commit it. When you are happy, click "Save Command". If you want to throw away your edits and go back to the command your software shipped with, click "Load Default", and "Cancel" backs out without saving anything.
Editing the command needs the startup command permission, so if you do not see the "Edit Command" button, ask whoever owns the server to grant it. To pick a different game or version instead of hand-editing the command, see Software.
Docker image#
The Docker image is the container your server runs inside, and it sets the software version and runtime your server boots into. When your software offers more than one image, the "Docker Image" box shows a dropdown so you can switch between them. Picking a different option applies right away.
If an administrator has set a custom image for your server, the dropdown is replaced by a notice telling you the image was set by hand and cannot be changed here. You can still revert to your software's default image from that notice, which opens a "Revert Docker Image" confirmation before anything changes.
Environment variables#
Environment variables feed values into your server at boot, and your software decides which ones show up. Each one sits in its own card with its name, the variable key, and a short description of what it does. Most are plain text fields you type into. A variable that only accepts on or off becomes a switch, which reads "On" and "Off" or "Enabled" and "Disabled" depending on the values it allows. A variable that has to be one of a fixed set of options becomes a dropdown of those exact values, and a variable whose default spans more than one line (a two-line MOTD, say) gives you a small text area so you can enter a real line break.
There is no save button for these. A change you make to a variable saves on its own about half a second after you stop typing or flip a switch, so you can edit a value and move on. If a value breaks the rule the variable enforces, the card turns up a red message and holds off saving until you fix it. Some variables check the value against your other settings too, so a Paper build number, for example, is only accepted once it matches the Minecraft version you picked. The cards lay out up to three per row and the page shows six variables at a time, with a pager underneath only when your software exposes more than six.
You can watch values take effect in the Console after a restart. To control who is allowed to edit these, see Users & permissions.
Global server variables#
Above your software's variables, the "Global Server Variables" panel lists values that Pyro fills in for you. You cannot type into these, but you can click any of them to copy it, and any of them can be used in your startup command. They come from your plan and your server's identity and network setup:
SERVER_MEMORYandSERVER_CPUcome from your plan's memory and CPU limits.SERVER_IPandSERVER_PORTcome from your default allocation. Change which allocation is the default on Networking.SERVER_NAMEandSERVER_UUIDare your server's name and its unique ID.
Things to watch for#
A variable that your software marks as locked shows a small padlock on its card and stays read-only, even for someone who otherwise has permission to edit variables. The same goes for the global server variables above, which are always filled in for you.