Loading...
Install Forge, NeoForge, or Fabric mods with the GaleniusNodes mod installer or manually. Includes dependencies, client requirements, and troubleshooting.
Install the correct Forge, NeoForge, or Fabric loader, then open Mod Installer in the GaleniusNodes game panel to search for and install compatible mods. If a mod is unavailable, stop the server and manually upload its jar and dependencies to the mods folder.
Minecraft mods can add dimensions, machines, creatures, biomes, performance improvements, and entirely new progression systems. A stable installation depends on matching the Minecraft version, mod loader, mod versions, and dependencies.
Back up the world before adding, updating, or removing mods. Removing a world-generation or content mod can permanently delete blocks, items, and entities from a save.
| Loader | Best suited for | Compatibility rule |
|---|---|---|
| Forge | Established mods and older modpacks | Use only Forge builds matching the Minecraft version |
| NeoForge | Many modern Forge-derived projects | Do not assume a NeoForge mod works on Forge |
| Fabric | Lightweight setups and optimization mods | Fabric mods require Fabric Loader and often Fabric API |
Choose the loader required by your mods or modpack. A Forge mod cannot normally run on Fabric, and a NeoForge release should not be assumed to work on Forge.
Before installing files, write down the exact Minecraft version and loader required by the mod. Check every dependency on the mod's official Modrinth, CurseForge, or GitHub page.
Changing server software can replace startup settings. Confirm you selected the existing world and create a backup first.
The GaleniusNodes mod installer lets you find and install supported mods directly from the game panel without downloading and uploading jar files.
Always verify the selected release matches Forge, NeoForge, or Fabric. A mod for a different loader will not start even when the Minecraft version matches.
Use this method when a mod or required version is not available in the installer. Stop and back up the server, download the correct release from the official Modrinth, CurseForge, or GitHub page, then upload each jar and required dependency directly into the mods folder.
/mods/ExampleMod.jar
/mods/RequiredLibrary.jarDo not extract mod jars. Avoid placing resource packs, shader packs, or Bukkit plugins in this folder because the loader cannot use them as mods.
Install the same Minecraft version and mod loader in the launcher. Copy all shared and client-required mod jars into the local Minecraft mods folder. Server-only mods do not need to be installed by players.
%appdata%\.minecraft\modsThe safest approach for a custom pack is to distribute an exported launcher profile so every player uses the same loader and mod versions.
Start the server and watch the first startup attempt. If it stops, locate the first meaningful error rather than the final generic crash message.
| Symptom | Likely cause | Fix |
|---|---|---|
| Mods tab is missing | No supported loader is installed | Install Forge, NeoForge, or Fabric first |
| Missing mandatory dependency | Required library is absent | Install the named dependency for the same loader and version |
| Mod is for a different loader | Forge, NeoForge, and Fabric builds were mixed | Replace it with the correct loader build |
| Mismatched mod channel list | Client and server mod versions differ | Make shared mods and versions identical |
| Server runs out of memory | The pack or world generation exceeds available RAM | Reduce the pack or allocate more RAM |
| World fails after removing a mod | Saved content depended on that mod | Restore the backup and follow the mod's removal guidance |
Use the panel's modpack installer when the pack is available. For a manual installation, use the pack's dedicated server pack, not the client export. Server packs exclude client-only files and usually include the correct startup configuration.
Once the server reaches the ready state and a matching client can join, the mod installation is complete.
Players need the same loader and all mods that add client-visible content or networking. Some performance and administration mods are server-side only; check each mod's documentation.
No in normal setups. Forge, NeoForge, and Fabric use different APIs. Download the build made for your loader or choose a supported alternative.
The player's loader, mod versions, or required dependencies do not match the server. Compare the client and server mods folders and use identical versions for shared mods.
Small modded servers often start around 4 to 6 GB, while large modpacks may need 8 GB or more. Player count, world generation, and the specific mods determine the real requirement.
The Mods tab requires a supported mod loader such as Forge, NeoForge, or Fabric. Install the correct loader for your Minecraft version before opening the mod installer.
The loader has not completed a successful first start. Install Forge, NeoForge, or Fabric, start the server once, then stop it before uploading mods.
No. Forge, NeoForge, and Fabric mods are built for Minecraft Java Edition and cannot be installed on a Bedrock Dedicated Server.
How to Use SFTP on a Minecraft Server
Connect to your Minecraft server with SFTP and FileZilla. Learn where to find GaleniusNodes credentials, upload worlds and server files, and fix connection errors.
Read guideHow to Change Your Minecraft Server Version
Change your Minecraft server version with the GaleniusNodes version changer. Learn how to back up your world, choose compatible server software, and fix common startup errors.
Read guideHow to Install Plugins on a Minecraft Server
Install Minecraft plugins with the GaleniusNodes plugin installer or manually on Paper, Purpur, and Spigot. Includes compatibility checks and troubleshooting.
Read guideInclude your Minecraft version, server software or loader, plugin or mod URL, and the first console error.