Skip to main content
The Startup page allows you to configure how your server starts, including Java arguments, memory allocation, and game-specific launch parameters.

​
Understanding Startup Variables

  • Server Variables
  • Docker Image
1

View Current Variables

Navigate to the Startup tab to see all configured variables
2

Common Variables

​
SERVER_JARFILE
string
default:"server.jar"
The server executable file name
​
VANILLA_VERSION
string
default:"latest"
Minecraft version to use (for vanilla servers)
​
STARTUP
string
required
Complete startup command with all arguments
​
MEMORY_LIMIT
number
default:"1024"
Maximum memory allocation in MB
3

Modify Variables

Click on any variable field to edit its value
Changes to startup variables require a server restart to take effect

​
Memory Configuration

1

Determine Memory Needs

Calculate memory requirements based on:

Player Count

  • 1-10 players: 1-2GB
  • 10-50 players: 2-4GB
  • 50+ players: 4GB+

Modifications

  • Vanilla: Base memory
  • Light mods: +25%
  • Heavy modpacks: +50-100%
2

Set Memory Allocation

Update the memory variables:
MEMORY_LIMIT: 1024
3

Verify Allocation

Check the startup command includes correct memory flags:
Minecraft Example
java -Xms128M -Xmx{{MEMORY_LIMIT}}M -jar {{SERVER_JARFILE}}

​
Java Arguments Optimization

  • Basic Arguments
  • Performance Tuning
  • Game-Specific
-Xms128M -Xmx{{MEMORY_LIMIT}}M
-XX:+UseG1GC
-XX:+ParallelRefProcEnabled
-XX:MaxGCPauseMillis=200

​
Game-Specific Startup Options

  • Minecraft Java
  • Minecraft Bedrock
  • Other Games
1

Server Type Configuration

SERVER_JARFILE: server.jar
VANILLA_VERSION: 1.20.4
2

Additional Arguments

Common Arguments
-Dfile.encoding=UTF-8
-Djline.terminal=jline.UnsupportedTerminal
-Dlog4j2.formatMsgNoLookups=true

​
Advanced Configuration

​
Environment Variables

1

Add Custom Variables

You can add custom environment variables for specific needs:
Examples
TZ=America/New_York (Set timezone)
LANG=en_US.UTF-8 (Set language)
JAVA_TOOL_OPTIONS=-Duser.timezone=UTC
2

Reference Variables

Use variables in your startup command:
java -Xmx{{MEMORY_LIMIT}}M -jar {{SERVER_JARFILE}} --port {{SERVER_PORT}}

​
Startup Command Customization

  • Command Structure
  • Custom Commands
Basic Structure
java [JVM_ARGS] -jar [SERVER_JAR] [GAME_ARGS]
​
JVM_ARGS
string
Java Virtual Machine arguments (memory, garbage collection)
​
SERVER_JAR
string
Path to the server executable file
​
GAME_ARGS
string
Game-specific startup arguments

​
Troubleshooting Startup Issues

Common Causes:
  • Invalid Java arguments
  • Insufficient memory allocation
  • Missing or corrupted server files
  • Port conflicts
Solutions:
  1. Reset to default startup command
  2. Check server logs for error messages
  3. Verify file permissions
  4. Contact support if issues persist
Symptoms:
  • High CPU usage
  • Memory errors
  • Frequent garbage collection
Solutions:
  • Increase memory allocation
  • Optimize Java arguments
  • Use Aikar’s flags for better GC
  • Monitor resource usage
Error Messages:
  • OutOfMemoryError
  • GC overhead limit exceeded
Solutions:
  • Increase MEMORY_LIMIT variable
  • Optimize server plugins/mods
  • Use memory-efficient Java flags
  • Consider upgrading server plan

​
Best Practices

Regular Testing

Test startup changes on a quiet server first

Backup Configuration

Document working configurations before changes

Monitor Resources

Watch CPU and memory usage after modifications

Stay Updated

Keep Java arguments current with best practices
Need help optimizing your startup configuration? Our support team can help you choose the best settings for your specific use case.