ServerCore Mod Guide (REDUCE LAG)

ServerCore Mod Guide: Lag Reduction and Optimized Settings

The ServerCore mod is a powerful server-side utility that can drastically improve performance on modded servers by giving you control over how entities are handled. Since it's a server-side mod, your players do not need to install it.

This guide will show you how to install ServerCore and provide a pre-optimized configuration that you can use to significantly reduce lag on your server.

IMPORTANT: Always back up your original config files before making changes. These settings are a strong starting point, but you may need to tweak them to fit your specific modpack and community.

Step 1: Installing ServerCore

1. Download the correct version of the ServerCore mod from its official CurseForge page, making sure it matches your server's Minecraft version.
2. Using the File Manager or FTP, upload the downloaded .jar file into your server's /mods folder.
3. Restart your server. This will load the mod and generate its default configuration files.

Step 2: Understanding the Configuration Files

ServerCore uses two main files for its settings, both located in the /config/servercore/ folder:

• optimization.yml: Contains simple on/off toggles for optimizations that have a very high performance gain with minimal impact on gameplay.
• config.yml: Contains the main, detailed features like mob caps and the powerful Activation Range system.

Optimized optimization.yml Settings

For most modded servers, it is safe and highly recommended to enable all optimizations in this file. These are the "easy wins" for performance.

Recommended optimization.yml

# Allows you to toggle specific optimizations that don't have full vanilla parity.
reduce-sync-loads: true
# Can significantly reduce the time spent on chunk iteration by only updating the ticking chunks list each second, rather than each tick.
cache-ticking-chunks: true
# Optimizes command block executions by caching parsed commands.
optimize-command-blocks: true
# Can significantly reduce time spent on mobspawning, but isn't as accurate as vanilla on biome borders.
fast-biome-lookups: true
# Fluid random ticks, like lava spreading fire, are run twice each game tick.
cancel-duplicate-fluid-ticks: true

Optimized config.yml Settings

This file controls the more advanced features. Our recommended settings focus on enabling the most impactful systems for entity control.

• Activation Range (Most Important): This is the single most effective feature. It makes entities far away from players process their AI less often, drastically reducing CPU load. We will enable it and also enable vertical checks, which is great for modern Minecraft's tall worlds.
• Breeding Cap: This prevents massive animal farms from lagging the server by limiting how many animals of one type can exist in a small area. We will enable this.
• Lobotomize Villagers: This is a must-have for servers with villager trading halls. It reduces the processing power of idle villagers who are stuck in a small space. We will enable this.

Key Sections of Optimized config.yml

You can replace these entire sections in your /config/servercore/config.yml file with the optimized versions below.

# In the "features" section
lobotomize-villagers:
  # Makes villagers tick less often if they are stuck in a 1x1 space.
  enabled: true
  # Decides the interval in between villager ticks when lobotomized.
  tick-interval: 20

# Replace the entire "breeding-cap" section
breeding-cap:
  # Enables breeding caps.
  enabled: true
  villagers:
    limit: 32
    range: 64
    unlimited-height: false
  animals:
    limit: 32
    range: 64
    unlimited-height: false

# Replace the top part of the "activation-range" section
activation-range:
  # Enables activation range.
  enabled: true
  # Briefly ticks entities newly added to the world for 10 seconds (includes both spawning and loading).
  tick-new-entities: true
  # Enables vertical range checks. By default, activation ranges only work horizontally.
  use-vertical-range: true
  # Skips 1/4th of entity ticks whilst not immune.
  skip-non-immune: false
  # Allows villagers to tick regardless of the activation range when panicking.
  villager-tick-panic: true

Step 3: Apply Changes and Restart

After you have replaced the content in both optimization.yml and config.yml with the settings above, simply Save both files and Restart your server from the console. Your server should now be running with significantly improved performance.