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 setup is ready.
5. Start or restart the server after install if it is not already running.

Installing after creation

Use Check profile to check every required CurseForge file in a friend's private profile before installing it. You need the server's Files permission, a matching Minecraft version and mod loader, and a stopped server for installation. Prefer an official server pack when the creator provides one. If imports are temporarily unavailable, use a public CurseForge server pack or contact support instead.

1. Open the server, then go to Mods & Plugins or Modpacks.
2. Select Modpacks.
3. Search CurseForge server-pack modpacks, select a project, and install a compatible file.
4. For a profile shared by a friend, paste the CurseForge profile code or supported CurseForge link into Check profile. Shared codes expire after 7 days, so ask the creator for a new code if it has expired.
5. Review the detected Minecraft version, mod loader, total required files, files ready for the server, confirmed client-only files skipped, and any blocked files. Confirmed client-only files are skipped on the server only; players keep them in their original client pack. Unknown required mods are never silently skipped. Kyrbit imports CurseForge files only by default; include bundled profile overrides only when you trust the creator and have reviewed the warning.
6. Existing files with the same names can be replaced, so create a backup before confirming the install. Then watch the console after restart for missing dependency or Java errors.

Installation stays blocked if required CurseForge files cannot be verified or downloaded. The check lists the affected files and reasons instead of skipping them. If the checked plan changes before installation, check the profile again and review the new plan. These checks cannot guarantee that a pack will start or that players can join; verify both after installation. Test on a clean server: previously installed client-only files are not removed.

Profile overrides exclude known executable and native formats, bundled Java archives, and script files (including KubeJS). Packs that require these files need a supported server pack. Other overrides may still contain untrusted content interpreted by mods.

If CurseForge marks a server-required file unavailable through their API, Kyrbit cannot bypass the author's distribution settings or mirror it automatically. Use an official server pack from the author or open a support ticket for an authorized alternative.

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. Mods required on both sides need matching versions. Client-only mods stay in players' packs and are not needed on 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.