Host a modpack

Start with the pack, not the loader#

A modpack normally fixes a Minecraft version, loader, mod list, configs and sometimes Java version. Use those exact requirements. Do not convert a Forge pack to Fabric or update the game version one component at a time unless you are prepared to maintain a fork.

Client pack means what players install. Server pack removes client-only files and adds server startup/configuration. They are related, not always identical.

Modrinth modpack#

1. 1
   Open the pack’s official Modrinth page and choose a specific version.
2. 2
   Read the description, changelog and dependency information.
3. 3
   Check whether the author publishes server files or server installation instructions.
4. 4
   Confirm the Minecraft version and loader: Fabric, NeoForge or Forge.
5. 5
   Download/import the client pack through Modrinth App or another launcher that supports the format.
6. 6
   Build the server using the pack’s official server method; do not upload the client instance blindly.
7. 7
   Accept the Minecraft EULA only after reading it, then start once.
8. 8
   Join with the exact client pack version.

CurseForge modpack#

1. 1
   Open the pack’s official CurseForge Files page.
2. 2
   Select the intended pack version—not simply the newest file.
3. 3
   Look for an additional file explicitly named Server Pack or follow the author’s server instructions.
4. 4
   Download that official server pack and read its README/start script.
5. 5
   Match the required Java and loader versions.
6. 6
   Set memory conservatively and start from a clean directory.
7. 7
   Share the normal client pack through CurseForge’s supported launcher flow.

If no server pack exists, ask the author/community for the supported server method. Removing client-only mods by trial and error can produce a server that starts but is not supported.

Custom modpack#

1. 1
   Pick one Minecraft version and one loader.
2. 2
   Add a few mods at a time from official sources.
3. 3
   Record environment: client-only, server-only or both.
4. 4
   Record every dependency and exact version.
5. 5
   Test a dedicated server and a clean client—not only single-player.
6. 6
   Export through a launcher format that references official project downloads.
7. 7
   Give the pack its own version number and changelog.
8. 8
   Back up the server before publishing an update.

Friends can use Modrinth App ↗, Prism Launcher ↗ or the CurseForge app ↗ where appropriate for the chosen format. Use official downloads and explain which profile replaces the old one.

One profile beats thirty downloads#

The Modrinth App ↗ can keep a client profile’s Minecraft, Fabric and mod versions together. It does not remove the need to respect each mod’s licence.

1. 1
   In Modrinth App, create a new profile for the exact Minecraft version.
2. 2
   Choose Fabric and a loader compatible with the server.
3. 3
   Add client-required and both-side mods from their project pages.
4. 4
   Do not include server-only optimization mods unless they also have a useful client role.
5. 5
   Launch and join the server from this profile.
6. 6
   Export the profile using Modrinth’s pack format.
7. 7
   Send the small exported pack file—not a random zip of other people’s jars.
8. 8
   Have each friend import it in Modrinth App and test before game night.

Keep everyone synchronized#

Record a pack version such as FriendsPack 1.3. When changing shared mods, update the server backup first, export a new profile version, and tell players exactly which old profile it replaces.

Licensing and redistribution#

Do not send a zip of mod jars unless every included license permits that redistribution. Prefer Modrinth/CurseForge pack formats, manifests and official server packs created by the pack author. A helper script should download only from official APIs/URLs and obey their terms.

Keep a server manifest with:

• Minecraft, Java and loader versions
• Pack name/version and official page
• Server pack file/version
• Additional server-only mods
• Removed client-only mods
• Config changes
• Last successful backup and restore test