CurseForge Server Hosting with Depot

If you want to run a CurseForge modpack on your host then you must download a server pack and transfer it through SFTP and determine the correct Java version. The Summer 2026 Blacksmith’s Portal update introduced Depot as the platform which allows users to find and download modpacks together with their mods and plugins and resource packs and datapacks and worlds from CurseForge and Modrinth.

This guide exists as a section within the Summer 2026 panel overview. For plans built for heavy packs, see modded Minecraft server hosting.

What CurseForge server hosting needs

A CurseForge modpack server consists of more than just a jar file and a world storage directory. You need:

• The correct Minecraft version
• The matching modloader (Forge, Fabric, NeoForge, Quilt, and so on)
• Every server-side mod and dependency the pack expects
• Enough RAM for the pack under load
• A Java runtime the loader accepts
• A way for players to install the same client pack

Manual installs usually fail in the middle of that list: wrong loader, missing deps, or a Java image that boots vanilla but crashes under Forge. Depot handles that checklist in one install flow.

What Depot installs

From Depot you can browse and install:

• Modpacks (CurseForge and Modrinth)
• Mods and plugins
• Resource packs and datapacks
• Worlds

The installation process shows better information than previous versions of the software. The system detects dependencies during its operation and it selects the suitable Minecraft version together with modloader runtime to enable your CurseForge modpack server to start with the correct Java version. You can delete all files before installing a new system when you want to start fresh but each action gets recorded in the system log.

How to install a CurseForge modpack on your server

1. Open your Minecraft server in the control panel.
2. Open Depot.
3. Filter or search CurseForge (or Modrinth) for the pack you want.
4. Optionally enable a wipe if you are replacing an existing world or mod set.
5. Click Install and watch progress. You can keep using the panel while it runs.
6. Start the server when the install finishes. If the egg needs a different Java image, the panel compares running vs required so the next step is clear.

AleForge provides CurseForge server hosting through its platform which lets users discover and set up servers and find proper runtime environments without requiring them to handle manual server pack operations.

Wipe vs keep world

Manual CurseForge packs vs Depot

You still have full file manager access (including Code Editor Mode) when you need a custom tweak after the pack lands: extra mods, config edits, or a datapack the catalog does not list.

Forge, Fabric, and Java

Common failure points:

• Loader mismatch. The Fabric client fails to connect with Forge server pack when players use it and the same issue occurs when players start with Forge. Players need to install the pack which duplicates the content they will use for their game launch.
• Java image. Modern loaders often need a newer Java than older packs. The program needs you to run the required Java image before you should start checking for crash logs.
• Mixed leftovers. The process of installing a CurseForge pack on top of an existing Technic or FTB leftover tree system creates an environment which leads to frequent crashes. The best approach involves performing a complete system wipe before you install the software from scratch while restoring only the world data which the pack allows.
• Client pack version. The server requires players to use the exact same version of CurseForge or Modrinth pack which the server installed. When players join with versions that are only close enough instead of exact, they will experience missing registry entries.

RAM and plan sizing for CurseForge packs

Vanilla RAM estimates do not apply. The system requires more available memory because it needs to load all its chunks and entities and machines.

1. Start from the pack author’s server RAM notes when they publish them
2. Prefer a plan with room to grow. Running out of memory mid-session is worse than oversizing slightly.
3. The system begins its initial startup process which leads to graphical resource displays on the monitor. The system requires memory expansion before it can accept additional users once memory usage reaches its maximum point.
4. Use Server Splitter style workflows when you want a test pack and a live SMP without sharing one fragile filesystem

Troubleshooting failed CurseForge installs

1. Backup and note the pack version before retrying
2. Wipe and reinstall if a previous install left half-written files
3. Apply the required Java image when prompted
4. Check console for loader errors (missing mods, bad mixin, wrong Minecraft version)
5. Confirm players are on the same pack ID and version from CurseForge or Modrinth
6. If you customized configs heavily, restore from backup rather than layering another install on top

Tips for a stable CurseForge modpack server

1. Backup first. Take a panel backup before swapping packs or wiping.
2. Match clients. Use the same CurseForge or Modrinth pack version as the server.
3. Size RAM for the pack, not for vanilla.
4. Use one installer path. Prefer Depot for catalog installs and avoid mixing in leftover manual server packs.
5. Update on a schedule, not in the middle of a raid night.

Related Summer 2026 tools

• Theme and productivity updates: pop-out console, hotkeys, and Code Editor Mode
• Palworld server settings: guided config editor for other games
• Project Zomboid mods: Workshop mod manager for PZ dedicated servers

For CurseForge server hosting with Depot installs, see modded Minecraft plans, Minecraft hosting, or the help docs.