Minecraft: Java Edition: Mods

Mods extend Minecraft’s functionality by adding new content, mechanics, or features. Unlike plugins (which only modify the server), mods typically require both the server and client to have matching installations.

Use the list below to find the guide that matches what you are doing.

Which guide do I need?

• Installing a ready-made pack from CurseForge (for example Better MC or All the Mods): use the Modpack Manager to install a premade modpack. This is the easiest path and works for most players.
• Installing a custom pack, or a pack that does not ship server files: install a modpack manually - including building a server pack from a client-only pack when the developer never released one.
• Adding a few individual mods to an existing setup: upload mods manually.
• Updating a pack, or switching to a different one without losing your world: update or switch your modpack.

Choosing a modloader

Every mod and modpack runs on a modloader, and each mod targets one of them. WinterNode supports both through the Edition Installer:

• Fabric - a lightweight, fast-updating modloader popular for performance mods and newer Minecraft versions.
• Forge / NeoForge - the original modloader with the largest mod ecosystem. NeoForge is its successor for Minecraft 1.20 and newer; some modern mods require it instead of Forge. They share a modding API but are installed separately.

If you are installing a premade pack, the Modpack Manager handles the modloader for you. You only need to pick one yourself when building a custom setup or adding individual mods - then install it with the Edition Installer.

Client-side, server-side, or both?

Any mod is one of three types - check each mod’s page before adding it:

• Client-side only - won’t run on a server; install it in your own client, not here.
• Server-side only - needed on the server; connecting players don’t need it installed.
• Both - required on the server and on every client that connects.