Understanding Modpack Types
Minecraft modpacks come in two flavors: Forge-based (traditional heavy modpacks like All The Mods, RLCraft, Enigmatica) and Fabric-based (lighter packs using Fabric mod loader). Forge packs dominate the popular launchers like CurseForge, Technic, and FTB. Fabric packs are newer, focus on performance, and work well with optimization mods like Sodium and Lithium. Choose your modpack before selecting a server type — Forge requires the Forge server jar, Fabric requires the Fabric server loader.
Using the One-Click Modpack Installer
Our control panel includes a one-click modpack installer with 200+ pre-configured modpacks. Navigate to the Modpacks tab, browse or search for your pack, and click Install. The installer handles everything: downloading the correct Forge/Fabric version, fetching all mod files from CurseForge, generating the eula.txt and server.properties, and setting the appropriate RAM allocation. Installation takes 2-5 minutes depending on modpack size.
Manual Modpack Installation
If your modpack isn't in the one-click library, you can install manually. Download the server files from the modpack's CurseForge page (usually a Server Pack zip). Delete the default world, mods, and config folders from your server. Upload the server pack files via the file manager or SFTP. Install the correct Forge or Fabric server version from the Startup tab. Allocate sufficient RAM (large packs need 6-10 GB minimum). Start the server and watch the console for errors — missing mods will show as red errors.
RAM Requirements by Modpack Size
Light packs (50-100 mods): 4-6 GB. Examples: Better MC, Valhelsia. Medium packs (100-200 mods): 6-8 GB. Examples: Enigmatica 6, Direwolf20. Heavy packs (200-300 mods): 8-12 GB. Examples: All The Mods 8, RLCraft. Massive packs (300+ mods): 12-16 GB. Examples: GreedyCraft, Dimension Hopper. Always add 2 GB headroom for world generation spikes. Our Minecraft 8 GB and 12 GB plans handle most heavy modpacks comfortably.
Optimizing Modpack Performance
Modpacks are resource-intensive — optimization matters. Add performance mods if missing: Sodium/Lithium/Starlight (Fabric) or OptiFine/FerriteCore (Forge). Pre-generate the world with Chunky before going public. Set view-distance to 8-10 (not 16) to reduce chunk loading. Remove client-only mods from the server (they cause crashes). Update Java to the latest version — modern modpacks require Java 17 or 21. Use Aikar's JVM flags with larger heap allocation for heavy packs.
Troubleshooting Common Modpack Issues
Server won't start: Check Java version — Forge 1.18+ needs Java 17, 1.20+ needs Java 21. Crashes on startup: Remove client-only mods (mods that add GUIs, keybinds, or shader support). Players can't connect: Verify client and server have identical mod lists — one mismatched mod prevents joining. World corruption: Delete the world folder and let the server regenerate it. Memory errors: Increase RAM allocation — modpacks need more RAM than vanilla.
FAQ
Related Tutorials
From the Blog
Was this guide helpful?
Join our Discord for more guides and direct help from our engineering team.