Startup Arguments & Custom Flags

Every server container kicks off with a specific command-line script. If you're an advanced admin, you can tweak these arguments to optimize garbage collection, allocate specific CPU threads, boost network tickrates, and fine-tune server engine variables.

1. Core Placeholder System

Your startup command features dynamic placeholders wrapped in double curly brackets. The panel automatically replaces these placeholders using real-time database details just before firing up 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 server authentication.
`{{LicenseKey}}`	String Key	Used for games needing developer authorisation 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] Don't Mess with Placeholders Do not modify, delete, or rename these placeholders (like changing {{MaxPlayers}} to a hardcoded 32). Doing so will break the launcher script parser, causing your server console to crash on startup.

2. Performance Optimisation Presets

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

Minecraft Optimisation (Aikar's Flags)

For Java-based servers, swapping standard GC arguments for Aikar's garbage collection parameters minimises 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, customising tickrates and thread allocation ensures buttery-smooth physics calculations:

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

3. Memory Allocations & OOM Crashes

Memory limits (-Xmx and -Xms for Java) are dynamically managed by the panel based on your active 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 container limit, the host operating system's OOM killer will instantly terminate your server instance.

4. Resetting to Defaults

If your server fails to start because of a syntax error in your custom startup command, don't panic:

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