Overview
Enable this server mode by settingMODPACK_PLATFORM, MOD_PLATFORM or TYPE to CURSEFORGE.
You need to specify a modpack to run using the CF_SERVER_MOD environment variable. CurseForge server modpacks are available together with their respective client modpacks at CurseForge Modpacks.
Environment Variables
| Variable | Required | Description |
|---|---|---|
TYPE | Yes | Set to CURSEFORGE |
CF_SERVER_MOD | Yes | Filename or path to the server modpack ZIP file |
CF_BASE_DIR | No | Directory where modpack is expanded (default: /data/FeedTheBeast) |
USE_MODPACK_START_SCRIPT | No | Use bundled start script (default: true) |
FTB_LEGACYJAVAFIXER | No | Apply legacy Java fixer workaround (default: false) |
Basic Usage
Using a Separate Modpack Directory
To keep pre-downloaded modpacks separate from your data directory, attach another volume:Modpack Data Directory
By default, CurseForge modpacks are expanded into/data/FeedTheBeast and executed from there. This location was chosen for legacy reasons when Curse and FTB were maintained together.
Change the directory by setting CF_BASE_DIR:
Advanced Configuration
Buggy Start Scripts
Some modpacks have buggy or overly complex start scripts. Avoid using the bundled start script by setting:Fixing “unable to launch forgemodloader”
If your server fails to load with an error like:Migration to Auto CurseForge
For better automation, upgrade tracking, and cleanup capabilities, migrate to Auto CurseForge.
- Automatic version upgrades
- File cleanup between versions
- API-based modpack installation
- Better mod exclusion/inclusion controls