Documentation
How to download AtlasSpigot, start it up, and change the settings.
Getting started
1. Pick your version
Every Minecraft version is its own release track — check the Downloads page for what's released vs. still planned, and which fork (Leaf or Purpur) each version is built on.
2. Download the jar
Grab AtlasSpigot-<version>.jar from that version's GitHub release. No account or login required — releases are public.
3. Accept the EULA
Create eula.txt next to the jar containing eula=true, or run the server once and edit the file it generates.
4. Start the server
Use the start.sh in that version's config folder in the repo — it has the JVM flags this project tunes and tests against — or run java -jar AtlasSpigot-<version>.jar yourself.
5. (Optional) Apply the tuned config
Each version's repo folder ships the exact config files (atlas.yml / atlas-global.yml, paper-global.yml, paper-world-defaults.yml, spigot.yml) this project tests against. Copy them in before first boot, or apply just the deltas listed on the What's tuned page.
Config file reference
| File | What lives here |
|---|---|
| atlas.yml / atlas-global.yml | Rebranded from purpur.yml / leaf-global.yml. Purpur/Leaf's own gameplay and (on Leaf tracks) performance-module settings. |
| pufferfish.yml | Leaf/Purpur tracks that bundle Pufferfish's patches (see What's tuned) — dab.enabled, inactive-goal-selector-throttle, and related mob/AI tuning live here. |
| config/paper-global.yml | Server-wide Paper settings — max-joins-per-tick and similar. |
| config/paper-world-defaults.yml | Per-world Paper settings — redstone-implementation, optimize-explosions, and similar. |
| spigot.yml | Legacy Spigot-era settings — entity-tracking-range, view/simulation-distance defaults. |
Not every file exists on every track — some older Purpur versions predate Pufferfish's merge and don't ship pufferfish.yml. Each version's own NOTES.md in the repo documents exactly what's present.
FAQ
Is this safe to use on a production server?
Every setting this project turns on is checked against upstream's own source, issue tracker, and any @Experimental/@Deprecated flags before it ships — see the What's tuned page for the full methodology and what was deliberately left off. That said, always keep backups regardless of which server software you run.
Will my plugins work?
AtlasSpigot is a source-rebuilt Leaf or Purpur (Paper-API compatible) — plugins built against the Bukkit/Paper/Purpur API work unmodified. Bukkit.getName() reports "AtlasSpigot" instead of the upstream fork's name, which matters only to plugins that specifically gate features on server-brand string checks.
Where do I report a bug?
Open an issue on the AtlasSpigot GitHub repo. If it reproduces on stock Leaf/Purpur too, it's also worth reporting upstream.
How is bStats data used?
AtlasSpigot reports to its own registered bStats project (id 33733) — real, publicly viewable usage data, not fabricated. See the Statistics section on the project README.
More detail on tuning specifically lives on the What's tuned page, and real performance numbers are on Benchmarks.