Modpacks need the server pack, not the client zip alone. Chapter22 Minecraft hosting highlights popular packs (ATM, Better MC, RLCraft, and similar) — installer UI can evolve, but the operator steps stay the same.
Before you install
- Backup the world if this server already has progress.
- Confirm the plan has enough RAM for the pack (RAM guide).
- Tell players which pack version to install on their launchers.
One-click / panel installer (when offered)
- Stop the server.
- Open the modpack/installer flow from the service or panel instructions provided after checkout.
- Select the pack → confirm → wait for download.
- Start and watch the console for Forge/NeoForge/Fabric banners and
Done.
Manual server-pack upload
- Download the server pack from the pack author (CurseForge/Modrinth/etc.).
- Stop the server. Upload/extract into the server root via SFTP or File Manager.
- Ensure the startup jar matches the pack (Forge/NeoForge/Fabric).
- Accept EULA again if the pack replaced
eula.txt. - Start and fix missing
mods/mismatches from the console log.
After install
- Set
max-players, difficulty, and whitelist. - Share the pack name + version in your Discord.
- Schedule backups before big updates.
Related guides
Frequently Asked Questions
Do players need the same pack?
Yes. Every client must run the matching modloader and pack version.
Out of memory on boot?
Heavy packs need more RAM — upgrade the tier or reduce JVM pressure.
Installer changed?
Chapter22 may iterate one-click installers. Use File Manager + official server pack zip as fallback.
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.