AtlasSpigot 26.2 - build 24 (Gale world config)

Config update. Same jar as build 23 (ten optimisation patches); this ships a config surface that was previously running entirely at stock.

New: gale-world-defaults.yml

The tuned bundle carried atlas-global, paper-global and paper-world-defaults but no Gale files at all — so while everything else was tuned hard, every Gale world setting was still on defaults. Two changes:

entities-can-random-stroll-into-non-ticking-chunks → false. Verified against Gale's patch rather than assumed: RandomStrollGoal refuses a destination in a non-ticking chunk. Mobs at the edge of the ticking area stop wandering outward, so they no longer generate activity in chunks nothing is simulating. The cost is that edge mobs pace within the loaded region instead of drifting out.

save-fireworks → false. Firework rockets aren't persisted, so any in flight vanish across a restart. Marginal, but free.

gale-global.yml is left at defaults. Its one candidate, increase-time-statistics, stays rejected — it turns CROUCH_TIME, TIME_SINCE_DEATH and TIME_SINCE_REST into sampled approximations, and TIME_SINCE_REST drives phantom spawning.

The rest of Gale's defaults are already tuned upstream: phantom and climbing-entity chunk loads off, check-stuck-in-wall reduced, projectile chunk loads capped.

Config: otherwise unchanged from build 17

⚠️ Still maximum tuning. hopper.disable-move-event is on, so shop, sorting and economy plugins will not see hopper transfers (set false in config/paper-world-defaults.yml to restore). Spawner mobs have no AI, monsters despawn at 28/48, mob caps cut ~43%, simulation distance 3.

Verified

Boots in 12.27s with zero errors, and gale-world-defaults.yml comes back byte-identical after the server writes it — neither setting was rejected or silently overridden.

Not measured

No performance figures are claimed. 26.2 was benchmarked against Paper and the result was too noisy to publish — see results-26.2.txt.