Pick software by content type, not by hype.
| Software | Best for | Notes |
|---|---|---|
| Paper | Plugins, performance SMPs | Preferred Spigot fork |
| Spigot | Legacy plugin guides | Fine; Paper is usually better |
| Forge / NeoForge | Large modpacks | Client + server mods |
| Fabric | Lightweight mods | Fast-updating ecosystem |
| Vanilla | Pure survival | No plugins/mods |
Chapter22 framing
- Plugin communities → Paper on a Dirt–Diamond plan.
- CurseForge-style packs → Forge/NeoForge/Fabric via the modpack path.
- Do not drop plugin JARs into a Forge
mods/folder and expect them to load.
Switching later
Changing loaders usually means a new world or careful conversion. Backup first.
Related guides
Frequently Asked Questions
Can I run plugins and Forge mods together?
Not on stock stacks. Use Paper/Spigot for plugins, or Forge/Fabric/NeoForge for mods.
What is Paper?
A high-performance Spigot fork — best default for plugin SMPs.
What do modpacks use?
Almost always Forge, NeoForge, or Fabric — see the pack page.
Need help?
If you are stuck after following this guide, open a ticket from the Chapter22 client area with the exact error, the port or DNS change you made, and whether the service listens locally (ss / Resource Monitor) but fails externally.
Build the server. Grow the community. Start your next chapter.