Installing CurseForge modpacks

Modpacks have specific Minecraft versions, mod loader versions, and Java versions. Read your modpack's documentation before starting.

Quick path during server creation

1. Create a Minecraft server and choose Forge or NeoForge.
2. Pick the exact Minecraft version your modpack requires.
3. Use the optional CurseForge modpack picker to choose a compatible server-pack file, then create the server.
4. If the author allows API installs and a compatible server pack exists, Kyrbit installs it after the server agent registers.
5. Start or restart the server after install if it is not already running.

Installing after creation

1. Open the server, then go to Mods & Plugins or Modpacks.
2. Select Modpacks.
3. Search CurseForge, select a project, and install a compatible file.
4. For private or unlisted CurseForge profiles, paste the CurseForge profile code into Install code.
5. Watch the console after restart for missing dependency or Java errors.

If CurseForge marks a file unavailable through their API, Kyrbit cannot mirror it automatically. Use an official server pack from the author or open a support ticket for help with a manual install.

Common gotchas

• Wrong Java version. Modern modpacks (1.20+) usually need Java 17 or 21 depending on the loader and Minecraft version. Older packs may need Java 8. The panel tries to match supported versions, but custom jars may need manual help.
• Out-of-memory on first start. Heavy modpacks need to generate config files on first launch — let the server crash and restart it once or twice before reporting an issue.
• Mismatched client/server mods. Players need the exact same mod versions as the server. Distribute your modpack via the CurseForge client or official pack tooling, not "here's a zip".

Big modpacks

Heavy modpacks (200+ mods, e.g. ATM10, FTB Skies Expert) are CPU-bound, not RAM-bound. They run, but tick rate on Naples value-tier hardware will not match a high-end gaming PC. We're transparent about this — see Performance tuning.