Startup Arguments & Custom Flags

Every server container starts with a specific command-line execution string. Advanced operators can modify these arguments to fine-tune garbage collection, allocate CPU threads, adjust network tickrates, and configure server engine parameters.

1. Core Placeholder System

Your startup command contains dynamic placeholders wrapped in double curly brackets. These variables are automatically replaced by the panel using active database values prior to starting your server container.

Placeholder	Replaced Value	Description
`{{MaxPlayers}}`	Numeric Count	Maps to the maximum slots configured on your dashboard.
`{{GSLT}}`	Game Server Login Token	Required for Steam matchmaking authentication.
`{{LicenseKey}}`	String Key	Used for games that require developer authorization tokens (e.g., FiveM).
`{{Port}}`	Number Port	The primary network socket assigned to your container.
`{{Ip}}`	IP Address	The local routing address of the host node.

[!CAUTION] Placeholder Integrity Do not modify, delete, or rename these placeholders (e.g., changing {{MaxPlayers}} to 32). Doing so will break the launcher script parsing, causing the server console to fail on startup.

2. Performance Optimization Presets

Adding specific flags to your startup parameters can dramatically improve server performance and eliminate lag spikes.

Minecraft Optimization (Aikar's Flags)

For Java-based servers, replacing standard GC arguments with Aikar's garbage collection parameters minimizes Java Virtual Machine (JVM) thread pauses:

-XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8m -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurviorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1

Rust Engine Tickrate Tuning

For Rust instances, optimizing tickrates and thread allocation ensures smooth physics calculations:

-batchmode +server.tickrate 30 +server.queriespersecond 2000 +server.threads 4 +fps.limit 256

3. Memory Allocations & OOM Crashes

The memory limits (-Xmx and -Xms for Java) are dynamically managed by the panel based on your selected subscription plan.

[!WARNING] Out-Of-Memory (OOM) Protection Do not manually append custom -Xmx or -Xms flags to the startup arguments string. If you allocate more memory in your startup script than your server's assigned plan container quota, the host operating system's OOM killer will instantly terminate your server instance.

4. Resetting to Defaults

If your server fails to start due to a syntax error in your custom startup command:

Navigate to Startup Arguments in the panel.
Select the Reset to Default action located below the input area.
Restart the server. The panel will restore the default verified launcher configuration.