Skip to content

AtlasSpigot 26.2 - build 14 (config only)

Choose a tag to compare

@AtlasStudioMC AtlasStudioMC released this 30 Aug 21:10
· 22 commits to main since this release

AtlasSpigot 26.2, built on Leaf ver/26.2.

This is a config-only release. AtlasSpigot-26.2.jar is byte-identical to the one in atlasspigot-26.2-13 (verified by SHA256) — the source and build did not change. If you are already running build 13, you do not need to re-download the jar; you only need the updated config.

What changed

Enabled fixes.vanilla-bug-fix.mc-301114 — the ring-buffer combat tracker.

Being precise about what this actually does, because the setting's name oversells it: Paper already fixes this memory leak, and that fix was already active here via max-tracking-combat-entries: 10240. This toggle adds no new protection. What it changes is the mechanism — Paper scans and trims the combat entry list on every damage event, while Leaf swaps in an EvictingRingList, an O(1) ring buffer that evicts the oldest entry automatically. Same cap, same outcome, cheaper per-hit path.

One caveat worth knowing: Leaf rounds the capacity up to the next power of two internally, so the effective bound is 16384 rather than the 10240 in the config. Still bounded, leak still fixed.

This came out of a full audit of every setting still disabled in 26.2. Six other candidates were reviewed and deliberately left off — ProtocolLib incompatibility, login-handshake concurrency, gameplay trade-offs, and datapack caveats. Each one and its reason is documented on the tuning page.

Downloads

  • AtlasSpigot-26.2.jar — the server jar (unchanged from build 13)
  • AtlasSpigot-26.2-config.zip — the tuned config, ready to drop in alongside the jar. New in this release; previously you had to copy these out of the repo by hand.

Config also lives in the repo root. Set eula=true before first boot.