Introduction

The Hytale Performance Saver plugin is designed to improve server stability by intelligently reducing resource usage during periods of high load. It dynamically adjusts server behaviour to prevent crashes while maintaining a playable experience for users.

Reading time: 5mins

Prerequisites / Disclaimers

• A running Hytale server

• Access to the Game Panel

• Permission to install mods via the Mod Manager

• Basic familiarity with JSON configuration files (if you wish to make changes to the defaults)

This plugin manages performance under load; it does not replace proper server sizing. Extremely under-provisioned servers may still experience degraded performance.

Purpose

Hytale servers can experience unpredictable CPU and memory usage depending on player behaviour. The Performance Saver plugin mitigates these spikes by:

• Limiting TPS to stable values

• Dynamically adjusting view radius under CPU or RAM pressure

• Triggering garbage collection when memory can be reclaimed

The goal is to keep the server responsive and prevent resource-related crashes without permanently allocating excess hardware.

Procedure

1. Install the Performance Saver Plugin

1. Open your Game Panel

2. Stop your server if it is running

3. Navigate to:

   Left Sidebar → Tools → Mod Manager
   
   

   

   Navigating to the Mod Manager

   
   

4. Locate Performance Saver

5. Click Install
   
   

   

   You can install mods by clicking the install button and waiting 3-5 seconds to complete

   
   

Once installed, the plugin JAR is placed automatically at:

/home/container/mods/nitrado-performance-saver-<version>.jar

No manual upload is required when using our bespoke Mod Manager tool.

2. Verify Installation

1. Start the server after installation

2. Observe the console and ensure successful startup

3. Ensure the JAR exists in:

/home/container/mods/

3. Create the Configuration File

The plugin does not generate a config automatically.

1. Create the following directory (if it does not exist):

/home/container/mods/Nitrado_PerformanceSaver/

2. Inside that directory, create:

config.json

Full path:

/home/container/mods/Nitrado_PerformanceSaver/config.json

4. Configure Performance Saver

Below is the full default configuration. You can copy this directly into config.json and adjust as required:

{
  "Tps": {
    "Enabled": true,
    "TpsLimit": 20,
    "TpsLimitEmpty": 5,
    "OnlyWorlds": [],
    "InitialDelaySeconds": 30,
    "CheckIntervalSeconds": 5,
    "EmptyLimitDelaySeconds": 300
  },
  "ViewRadius": {
    "Enabled": true,
    "MinViewRadius": 2,
    "DecreaseFactor": 0.75,
    "IncreaseValue": 1,
    "InitialDelaySeconds": 30,
    "CheckIntervalSeconds": 5,
    "RecoveryWaitTimeSeconds": 60,
    "GcMonitor": {
      "Enabled": true,
      "HeapThresholdRatio": 0.85,
      "TriggerSequenceLength": 3,
      "WindowSeconds": 60
    },
    "TpsMonitor": {
      "Enabled": true,
      "TpsWaterMarkHigh": 0.75,
      "TpsWaterMarkLow": 0.6,
      "OnlyWorlds": [],
      "AdjustmentDelaySeconds": 20
    }
  },
  "ChunkGarbageCollection": {
    "Enabled": true,
    "MinChunkCount": 128,
    "ChunkDropRatioThreshold": 0.8,
    "GarbageCollectionDelaySeconds": 300,
    "InitialDelaySeconds": 5,
    "CheckIntervalSeconds": 5
  }
}

5. Key Configuration Areas

TPS Limiting (Tps)

• Caps maximum TPS for stability

• Applies a lower TPS limit when the server is empty

• Helps avoid CPU spikes and tick instability

Dynamic View Radius (ViewRadius)

• Reduces view radius automatically during CPU or RAM pressure

• Gradually restores view radius once the server recovers

• Prevents crashes during heavy chunk loading

Garbage Collection Controls

• Monitors JVM heap usage and chunk unloading

• Triggers garbage collection when memory is likely reclaimable

• Reduces long-term memory pressure

6. Apply Changes

1. Save config.json

2. Restart the server

3. Monitor logs and performance metrics after restart.

   1. Hint: Changes come up in the in-game chat!

Changes only take effect after a restart.

End

Performance Saver is best used as a safety net rather than a replacement for adequate resources. For most servers, the default configuration provides a good balance between performance and stability.

See our offers!

Need support?