Save 15% on your first purchase with code:
Minecraft

Installing modpacks on Forge or Fabric

Deploy CurseForge, FTB or Modrinth modpacks on your WingNode server with automatic jar and config setup.

Modpack install on WingNode is a two-step process: upload the pack, then set the startup jar. Wingman AI can handle both if you give it the modpack URL.

Method 1 — Panel modpack installer

Open Settings → Startup. Paste the CurseForge or FTB modpack ID (or direct zip URL). Click Reinstall. The panel downloads the pack, extracts the jars, updates the startup command and starts the server.

Method 2 — Manual upload

  1. Download the modpack server files from the pack's official site.
  2. Upload the archive to / via SFTP.
  3. Extract and move files so forge-*.jar sits at the root.
  4. Update the startup command in Settings → Startup to reference the new jar (e.g. java @user_jvm_args.txt @libraries/net/minecraftforge/forge/*/unix_args.txt).
  5. Restart.

RAM recommendations for modpacks

  • Light packs (SkyFactory 4, Valhelsia) — 4 GB minimum.
  • Mid packs (ATM8, Create Above and Beyond) — 6–8 GB.
  • Heavy packs (ATM9, FTB Ultimate, GregTech New Horizons) — 10–16 GB.

Updating a modpack

Back up the world first, then reinstall with the new pack version. Most packs preserve world compatibility across minor updates but break on major jumps (1.18 → 1.19).

Common issues

  • Missing mod on client — every client player must install the exact same version.
  • Duplicate mod — Forge refuses to start if two mods have the same modid; remove one.
  • Out of PermGen / Metaspace — bump RAM or add -XX:MetaspaceSize=256M.