Installation & Setup
Installation & Setup
Complete step-by-step guide to installing the Minecraft Modpacks plugin, configuring eggs, and preparing your server for modpack installations.
Prerequisites
- Pelican Panel version 1.0.0+ installed and running
- PHP 8.1, 8.2, or 8.3 on the Panel server
- A Minecraft server managed by the Panel
storage/andbootstrap/cache/writable (permissions0755, owner: web server user)- Database user with CREATE TABLE privileges
Step 1: Install the Plugin
- Download the latest
minecraft-modpacksplugin release - Place it in your Pelican Panel's
plugins/directory:/var/www/pelican/plugins/minecraft-modpacks/ - Clear the application cache:
php artisan cache:clear php artisan config:clear php artisan view:clear - Verify the plugin appears under Admin Panel → Plugins
Auto-Seeder
The plugin runs its seeder automatically on every panel boot (wrapped in try-catch for safety). The seeder creates:
- Minecraft Modpack Installer egg — Used during download, features:
['eula', 'java_version', 'minecraft', 'modpacks', 'plugins', 'mods', 'installer'] - Minecraft Modpack Runtime egg — Standard Minecraft server egg
Docker images configured: Java 8, 11, 16, 17, 21.
Step 2: Configure the Egg
The plugin uses the modpacks feature flag.
- Go to Admin Panel → Eggs
- Edit your Minecraft server Egg
- Add
modpacksto the Features field:["modpacks"] - Click Save
Feature flag must be exactly
modpacks(lowercase). The auto-created eggs already have this feature.
Step 3: Verify Eggs
After first load, verify both eggs exist:
| Egg | Purpose | Key Features |
|---|---|---|
| Minecraft Modpack Installer | Handles download + extraction | Has MODPACK_PROVIDER, MODPACK_ID, MODPACK_VERSION_ID variables |
| Minecraft Modpack Runtime | Runs the modpack server | Standard Minecraft features |
The installer egg's variables are populated automatically during installation.
Step 4: First Use
- Navigate to your server → click Modpack Browser in the sidebar
- Provider tabs appear: Modrinth, CurseForge, ATLauncher, FTB, Technic, VoidsWrath
- Browse or search for a modpack
- Ready to install!
Verification Checklist
| Check | Expected | If failing |
|---|---|---|
| Plugin in Admin → Plugins | Listed | Clear cache, check path |
| "Modpack Browser" in sidebar | Visible | Feature flag missing (modpacks) |
| Installer egg exists | "Minecraft Modpack Installer" in Eggs | Seeder didn't run — check logs |
| Runtime egg exists | "Minecraft Modpack Runtime" in Eggs | Seeder didn't run |
| Provider tabs visible | 6 tabs | JS/network error |
Troubleshooting
Plugin not visible
- Clear all caches:
php artisan cache:clear && php artisan config:clear && php artisan view:clear - Check
plugin.jsonexists in plugin root - Check
storage/logs/laravel.logfor errors
Eggs not auto-created
- Seeder runs on every boot — check logs for seeder errors
- Manual creation: copy egg configurations from plugin documentation
- Database user may lack CREATE TABLE privileges
"Modpack Browser is not available for this server"
- The plugin calls
abort(403)when themodpacksfeature is missing from the egg - Add
modpacksto the egg's features and save