Skip to main content
Startup parameters control how your server starts and behaves. Each server has configurable variables based on its Egg configuration, allowing you to customize memory limits, game modes, world settings, and more.

Understanding Startup Variables

Startup variables are placeholders in the startup command that get replaced with actual values:
Example Startup Command
Variables like {{SERVER_MEMORY}} are replaced:
Actual Command

Viewing Startup Configuration

Get startup information for your server:
Get Startup Info
Response

Variable Properties

  • name - Human-readable variable name
  • description - What the variable does
  • env_variable - Environment variable name
  • default_value - Default if not customized
  • server_value - Current value for this server
  • is_editable - Whether users can modify it
  • rules - Validation rules
Only variables with is_editable: true can be modified by users. Admin-only variables are hidden or read-only.

Updating Variables

Modify a startup variable:
Update Variable
Response
1

Navigate to Startup

Go to the Startup tab in your server panel.
2

Modify Variables

Edit the variables you want to change. The interface shows current and default values.
3

Save Changes

Click Save. The new values are validated against the rules.
4

Restart Server

Restart your server for changes to take effect. Variables are only applied at startup.

Common Variables

Minecraft Variables

The jar file to execute. Common values:
  • server.jar - Vanilla Minecraft
  • paper.jar - Paper server
  • spigot.jar - Spigot server
  • forge.jar - Forge modded server
Which version to download/run:
  • latest - Latest release
  • 1.20.4 - Specific version
  • 1.19.2 - Older version
For Paper/Spigot:
  • latest - Latest build
  • 450 - Specific build number
Forge version for modded servers.

Source Engine Variables

Steam App ID:
  • 730 - CS:GO
  • 232330 - CS2
  • 4020 - Garry’s Mod
  • 232250 - Team Fortress 2
Starting map for the server.
Game mode configuration.

Generic Variables

Memory allocation in megabytes. Usually auto-set based on server limits.
Primary allocation port. Auto-set from network allocations.
IP address to bind to. Usually 0.0.0.0 for all interfaces.

Variable Validation

Variables have validation rules:

Common Rules

  • required - Must have a value
  • string - Must be text
  • integer - Must be a number
  • boolean - Must be true/false
  • max:20 - Maximum length
  • in:value1,value2 - Must be one of listed values
  • regex:/^[a-z]+$/ - Must match pattern
If validation fails:
Error Response

Docker Images

Servers run in Docker containers with specific images:
Available Images
Some eggs allow users to select the Docker image. This is useful when different game versions require different Java versions.

Changing Docker Image

If allowed by the egg configuration:
Update Docker Image
Success
Changing the Docker image requires a server restart. Ensure the new image is compatible with your server software.

Read-Only Variables

Some variables cannot be modified by users:
Read-Only Variable
These are typically:
  • Resource limits (memory, CPU)
  • Network configuration (IP, port)
  • Security settings
  • License keys
Only administrators can modify read-only variables.

Environment Variables

All variables are passed as environment variables to the container:
Inside Container
Startup scripts can access these in any language:
Bash
Python

Startup Command Preview

The panel shows the final startup command with variables replaced:
Raw Command
Processed Command
This helps verify your variables are set correctly.

Activity Logging

Variable changes are logged:
Example Log

Common Configurations

Paper automatically downloads the specified version on first start.
Forge version must match Minecraft version.

Best Practices

Always test your server after changing variables. Check logs for errors related to invalid configurations.
For production servers, use specific version numbers instead of “latest” to prevent unexpected updates:
If you modify variables from defaults, document why:
  • Take screenshots of working configurations
  • Note dependencies between variables
  • Keep a changelog of what you changed
When changing versions, verify compatibility:
  • Plugin versions match server version
  • World format is compatible
  • Forge/mod versions align

Troubleshooting

  • Check server logs for error messages
  • Verify variable value is valid (check rules)
  • Revert to previous working value
  • Ensure Docker image supports the configuration
  • Check if is_editable is false
  • Verify you have startup.update permission
  • Some variables are admin-only
  • Contact server owner/admin
  • Read the validation rule carefully
  • Check for typos in your value
  • Ensure correct data type (string vs integer)
  • Stay within length limits
  • Restart the server after changing variables
  • Variables only apply at startup, not runtime
  • Check if game-specific config file overrides them
  • Verify variable name matches exactly