How ServerPackCreator Creates a Server Pack

Updated

ServerPackCreator builds a server pack by taking a Minecraft modpack you already have and producing a separate, server-ready copy of it. You point it at the modpack instance, choose which files and mods belong on the server, and it generates a new folder or archive containing only the server-side content. The exact steps below describe the general workflow; the tool's own documentation is the authoritative source for current options and supported modloaders.

What you need before starting

  • A Minecraft modpack instance that already runs on the client (CurseForge, Modrinth, or a similar launcher format).
  • Access to the modpack's folder on disk, including its mods, config, and manifest files.
  • A destination folder where the generated server pack will be written.
  • Java installed if you intend to run the resulting server.

The basic workflow

1. Select the source modpack

You give ServerPackCreator the path to the modpack instance. It reads the manifest and the mods directory to understand what the pack contains. This is the input: an existing client modpack.

2. Choose what goes into the server pack

Not every client mod belongs on a server. ServerPackCreator lets you mark mods and files as client-only so they are excluded. The expected result of this step is a filtered file list — the server pack should contain only what the server needs to run.

3. Configure server-specific settings

You set options such as the server pack name, the destination directory, and any files you want copied or overwritten. These settings determine the shape of the output.

4. Generate the pack

ServerPackCreator assembles the output: it copies the selected mods and configs, applies your settings, and writes the server pack to the destination. The output is a folder (and optionally an archive) that can be uploaded to a server host or run locally.

5. Verify the result

Start the generated server once to confirm it launches without missing-mod or config errors. If it fails, the usual cause is a client-only mod that was left in, or a config file that references client-side features.

Key things that affect the outcome

Factor Why it matters
Client-only mods Leaving them in causes server crashes or startup errors
Config files Some configs are client-specific and must be adjusted or excluded
Modloader version The server pack must match the modloader the modpack uses
Destination path Determines where the output lands and whether it overwrites existing files

Common sticking points

  • Missing mods on the server: usually a mod that was incorrectly excluded, or a dependency not carried over.
  • Server won't start: often a client-only mod still present, or a Java version mismatch.
  • Config errors: configs copied from the client may reference settings the server doesn't support.

For the current list of supported modloaders, exact menu options, and any version-specific behavior, check the ServerPackCreator documentation directly, since these details change between releases.