Deploy a CurseForge modpack to HostChicken

Deploy a CurseForge modpack to HostChicken

CurseForge packs are popular and well‑maintained—and deploying them to your HostChicken server is straightforward once you know which file to use. This step‑by‑step guide covers both scenarios: using an official server pack (easiest) and converting a client pack when no server pack exists.

Prerequisites

• A CurseForge modpack chosen and its version noted (e.g., 1.20.1, Forge or Fabric)

• Access to your HostChicken server dashboard

• A recent manual backup before changes

Option A: Use the official server pack (recommended)

1) Download the server pack

• On the CurseForge modpack page, go to Files.

• Filter for Server Packs if available.

• Download the `.zip` server pack matching your desired version.

2) Extract and review

• Extract the archive locally.

• Verify it contains `mods/`, `config/`, a server start script, and (for Forge) libraries or an installer jar.

3) Upload to HostChicken

• Stop your server and take a manual backup.

• Upload the extracted contents to your server files (root unless the readme says otherwise).

4) Start and validate

• Start the server. The first boot might take a while as dependencies download.

• Watch logs for missing mod messages or version mismatches.

5) Invite players

• Share the address and ensure everyone installs the same client pack version via the CurseForge app.

Option B: Convert a client pack to a server install

Use this when a server pack isn’t available.

1) Download the client pack

• From the Files tab, download the profile `.zip` for the version you want.

2) Prepare the server loader

• Determine the loader: Forge or Fabric.

• Forge: Download the Forge installer for the pack’s MC version. Run "Install server" locally to generate `forge-...-server.jar` and `libraries/`.

• Fabric: Download the Fabric server installer for the exact version and produce a server launch jar.

3) Remove client‑only mods

• Extract the client pack and open `mods/`.

• Remove minimaps, HUD/UI mods, shader loaders, and any client‑flagged mods from the upload set.

• Keep server‑required mods only. Refer to mod pages if unsure.

4) Upload to HostChicken

• Stop the server and back up.

• Upload `mods/`, `config/`, the loader server jar, and any `libraries/` required by Forge.

5) Start and resolve issues

• Start the server and read logs for missing dependencies.

• Add any named dependencies in the exact versions required.

6) Playtest

• Launch the same pack on your client (via CurseForge app) and connect.

Memory, flags, and performance

• Light packs: 2–4 GB RAM

• Medium packs: 4–6 GB RAM

• Heavy packs: 6–8 GB+ RAM

Don’t over‑allocate. Combine sensible RAM with view distance 8–10 and simulation 5–7, and consider nightly restarts for stability.

Updating the server pack safely

1. Clone or stage: Test updates on a copy of your server.

2. Backup: Always take a pre‑update snapshot.

3. Apply: Replace `mods/` and `config/` as instructed by the pack author.

4. Validate: Boot, watch logs, and play for 15–30 minutes.

5. Roll out: Update the live server during a maintenance window.

Common pitfalls

• Wrong pack flavor: Some packs publish multiple branches; choose the one matching your group and loader.

• Partial uploads: Use an upload method that preserves folder structure and file names.

• Client‑only leftovers: Minimap/shader mods on the server cause crashes.

• Loader mismatch: Forge/Fabric must match on both server and clients.

Quick checklist

• [ ] Download server pack (or convert the client pack)

• [ ] Prepare correct Forge/Fabric server jar

• [ ] Remove client‑only mods before upload

• [ ] Start, watch logs, fix missing deps

• [ ] Invite players with the same client pack version

With these steps, most CurseForge packs deploy cleanly to HostChicken in one attempt. If something breaks, restore, adjust, and try again—you’ll have a smooth routine after your first success.