How do I edit, reset, or roll back my startup command — do I need a ticket?
On this page
Most of your startup configuration is self-serve — you can adjust variables yourself on the Settings page without ever opening a ticket. Only a few admin-locked cases need our help.
What you can change yourself
On the Settings page you can edit variables like the JAR file name, the RAM buffer, minimum RAM, and any Java flags that are exposed — all without a ticket.
When you need a ticket
Some servers have the Docker image or startup command locked by an admin, showing a note that it "cannot be changed through this UI." If you need a change to a locked command or image, open a ticket and we'll handle it.
If an edit breaks startup
- Revert the specific variable you changed back to its previous value.
- Start the server and confirm it boots.
- If you can't revert it yourself, open a ticket — we can reset it for you.
Tip: Change one variable at a time and test between changes. That way, if the server won't start, you know exactly which value to roll back.
Frequently asked questions
Do I need a ticket to change the RAM buffer or JAR name? No — those are self-serve variables on the Settings page. Edit them freely.
Why is my startup command locked? An admin has locked the Docker image or command for that server. To change it, open a ticket and we'll adjust it for you.
More in Startup Command & Java
- What Java version do I need (17 / 21) and how do I set it?
- Can I use custom startup flags (MaxRAMPercentage, -nogui, velocity flags, OpenJ9)?
- Should Xms and Xmx be equal? What values?
- My startup command "looks weird" / shows ./bedrock_server — is that normal?