STYGION Documentation Search the docs

What it is

The fixes we wrote while chasing lag on a big Create / Sable server: what each kind does, how to install it, how to switch a part off, and what it never touches.

Updated 3 min read
On this page 5 parts
  1. Install
  2. What it does
  3. Switching a part off
  4. What it never does
  5. Other mods

STYGION Optimize is the pile of fixes we wrote while chasing lag on STYGION MC, a big Create Aeronautics pack. A fix either computes the same result with less work, or closes a bug that sits between two other mods. Each has its own switch, and the few that change behaviour a little are off until you turn them on.

Install

#

One jar for NeoForge 1.21.1 (Java 21), from CurseForge. It works on a server alone, in a client alone, or on both; a player does not need it to join a server that has it. Nothing is required next to it: the parts for other mods do nothing until that mod is installed.

At start the log has one line, STYGION Optimize <version> config loaded: …, saying what is on, and one line per other mod it found (Sable plots hooks applied …). A part whose mod is missing says (… not installed).

What it does

#

Crash and freeze fixes (on):

  • A move of millions of blocks, or one that is not finite, is dropped before collision walks every chunk on the way and the watchdog kills the server (movementGuard).
  • Sable: a teleport into a ship's plot (a bed or waystone on a ship, commands, joining) lands on the ship where it is now (sablePlotGuard).
  • Create: Deep Seas: its float check no longer walks millions of empty blocks for a ship with absurd numbers (submarineFloatScanGuard).
  • Better Chunk Loading: a player leaving no longer crashes the server (betterChunkLoadingLogoutFix).

Bugs between other mods (on):

  • Create Big Cannons with FTB Chunks: a cannon breaks and wears only what FTB Chunks lets an explosion break. Claimed bases stay whole unless their team allows explosions; shells still fly, hit, hurt and explode (cannonClaimGuard, 0.4.3).
  • Carry On: players are no longer disconnected when another player carrying something comes into view (carryOnSyncSnapshot).

Less work, the same result (on): player files, statistics and advancements written off the main thread; light copies that share what did not change; spawning, pathfinding and advancement checks that skip work whose answer is already known; Sable, NTGL, ParCool x Sable, Explorer's Compass, Ad Astra and Atmosphere asked less often or without the garbage. Every switch, with the words of the config file: Every switch.

Optional (off, they change behaviour a little): sparser AI for mobs far from every player (farMobAi), brainless mobs from mob farms (spawnerFarmMobs), a player in an unloaded chunk waiting alone instead of the whole server (playersDontWaitForChunks).

Switching a part off

#

config/stygion_optimize-common.toml, one line a switch: true on, false off. The file is read again while the server runs, so you can compare a part on and off in one session. config/stygion_optimize-startup.toml holds what has to be known before the world loads (blocks of removed mods) and needs a restart.

What it never does

#

It sends nothing anywhere: no connections, no telemetry, no update check. It reads and writes only the files Minecraft itself uses, and its two configs. It does not pregenerate, cap players or switch a feature off to hide a cost.

Other mods

#

Their authors' logic is left alone: Optimize touches another mod only where a profiler or a crash pointed, and every such part names the mod in the config. A bug we find in another mod is reported to its authors too; the fix here stays until their release has it. If you wrote one of those mods and want a part changed or removed, tell us on Discord.

Did this page help?

Opens the feedback panel with this page attached. It lands in the same queue as everything else.