Modpacks

How to deploy a custom CurseForge modpack

Install a CurseForge export ZIP or share code on your STIPE server, choose a server profile, and check the conversion from a client pack to a working server.

By STIPE Support · 5 min read · Reviewed 16 Nov 2026

Install Your Custom Modpack-7

Choose your installation method

For a published pack, first try Settings → More Modpacks Mods & Datapacks → Browse modpacks → CurseForge. Search for the pack, select its release and follow the installation confirmation.

For your own pack or a release you downloaded yourself, use Upload a pack → CurseForge ZIP. You can also install a temporary CurseForge profile code through Share code.

Use a proper CurseForge export or a compatible server package. Zipping only a mods folder is not the same as exporting a CurseForge profile. If you are starting from scratch, see Create a custom pack in the CurseForge app.

Upload and install a ZIP

1)

Prepare the exported pack Prepare the ZIP. In the CurseForge app, open your tested profile's three-dot menu, choose Share Profile and Export as .zip. Include the pack's required configuration and other content. Keep the ZIP intact.

2)

Stop the server In the STIPE Control Panel, stop your server and wait until it is fully stopped.

3)

Open the ZIP uploader Open Settings → More Modpacks Mods & Datapacks. Choose Upload a pack → CurseForge ZIP. If the installer shows cards, use Upload CurseForge ZIP.

4)

Upload and wait for transfer Drag the ZIP into the upload area or click Browse Files. The uploader displays its maximum file size. Wait for both upload and transfer to the game server to finish; 100% upload is not the installation-complete message.

5)

Select the uploaded package Under CurseForge Installer, choose the file in Select CurseForge export/server package. Uploading the ZIP alone does not install it.

6)

Review filtering and begin installation Review the client-only removal options below, then click Install selected CurseForge package.

7)

Choose the destination profile In the profile confirmation, choose Create new profile and install for a separate installation. Choose Continue on [profile name] only when you intend to replace/update files in that active profile. Confirm the displayed name before proceeding.

8)

Wait for completion Wait for the final installation result. Do not switch profiles or start another install while downloads, extraction and loader setup are still running.

Install with a share code

1)

Generate a current share code Obtain a current profile code using Share Profile → Generate Code in the CurseForge app while signed in. See the sharing guide for player import steps and code expiry.

2)

Enter the code in STIPE Stop the STIPE server, open Settings → More Modpacks Mods & Datapacks → Share code, and paste the code or supported link into Share code or link. In the card layout, choose Use a share code.

3)

Confirm options and install Review the filtering options, then click Install shared CurseForge modpack. Select a new or current profile in the confirmation and wait for installation to complete.

If the code has expired or the share cannot be downloaded, generate a fresh code or use the exported ZIP method.

Understand client-only mod removal

STIPE Client-only Mod Removal (Recommended) uses STIPE's curated detection to help prepare a client pack for a dedicated server. Keep it enabled for a normal client-export conversion unless you have a specific reason to change it.

Community Client-only Mod Detection (Optional) applies broader checks. It can find additional client-only mods, but can also disable something the server needs. Leave it off initially unless you need those extra checks.

Review Skipped and disabled files when it appears. Automatic conversion helps with common client-only mods and server setup, but it cannot guarantee that every custom collection of mods works together. Client-only mods can remain in the players' client pack even when they are excluded from the server.

Start and test the server

1)

Start the installed pack Once the installer reports success, click Start and open Console. Wait for full startup; the first launch of a large pack may take several minutes.

2)

Connect with the matching client Launch the matching client pack on your computer and connect using the address shown by STIPE.

3)

Test and share the release Test the pack's key features, then share the matching client release with your players.

Updating and troubleshooting

When updating the same pack, stop the server, keep a current backup and read the pack author's update notes before choosing the current-profile option. Pack files and configuration can be replaced. For a different pack, choose a new profile and world.

  • The package is not listed: wait for transfer completion, check the ZIP format and refresh the installer.
  • Automatic downloads are unavailable: follow the download/upload option shown, using the file the provider permits you to download.
  • The server crashes: inspect Console for a missing dependency, incompatible version or client-only mod. Check the skipped-file report. If broader community detection disabled a required server mod, retry with that optional detection off.
  • The server starts but a player cannot join: match the exact client pack release, loader and required mods.

Contact STIPE Support with the pack link or export details, release and exact error if you need help.

Earlier video walkthrough

This video shows an earlier interface. Follow the written steps above for the current controls and installation options.