How to Set Up a Cobblemon Server: RAM, Mods and Settings

Published on | Updated

Set up Cobblemon 1.8.4 on Minecraft 1.21.1 and Java 21 with the right loader and dependency versions, a recovery copy and RAM chosen for the complete mod list.

Cobblemon server setup

Cobblemon 1.8.4 was released on 27 October 2026 for Minecraft 1.21.1 on Fabric and NeoForge. The server needs Java 21 and the same loader as every player: Fabric with Fabric API, or NeoForge with Kotlin for Forge. Before choosing Cobblemon server hosting, decide whether your group uses the standalone mod, an official Cobblemon modpack or another pack that includes it. That choice determines which files you need.

The 1.8.4 changelog fixes what the team calls "heaps of spawns not working", a crash when a Fearow you are riding blinks, Minior's Shields Down ability, and blank Cooking Pot recipe book entries and missing tabs on Fabric. Another entry only says "Fixed something sneaky. I'll tell you about it later." The notes list no new config options or game rules. When you diagnose a server problem, read the release notes alongside the server logs and the complete mod list.

Choose the mod or the complete modpack

The standalone mod releases and official modpacks are separate downloads. Both official modpacks also received version 1.8.4 on 27 October, but another author's pack may follow a different schedule.

If your group plays a larger pack, use its matching server files and instructions. Replacing only its Cobblemon jar can leave the rest of the installation on a different set of dependencies. Write down the exact pack name and version before asking players to update.

Match Minecraft, the loader and the dependency

The Fabric and NeoForge mod files both target Minecraft 1.21.1. Choose the file for the loader your server and players use. The Fabric release lists Fabric API as required; the NeoForge release lists Kotlin for Forge.

These requirements are written into the 1.8.4 jars, next to what the official 1.8.4 modpacks run:

FabricNeoForge
Minecraft1.21.11.21.1
LoaderFabric Loader 0.17.2 or newerAny NeoForge 21.1 build, but use 21.1.195 or newer (see below)
Required modFabric API 0.116.6+1.21.1 or newerKotlin for Forge 5.10 or newer
Java21 only21 only
Official 1.8.4 modpackFabric Loader 0.20.1 with Fabric API 0.116.17NeoForge 21.1.264 with Kotlin for Forge 5.12.0

The 1.8.2 and 1.8.3 jars list exactly the same requirements, so 1.8.4 changes nothing about the loader or Java compared with 1.8.3. On NeoForge there is one catch for servers coming from 1.8.2. The jar accepts any NeoForge 21.1 build, but since 1.8.3 Cobblemon's mixin settings ask for MixinExtras 0.5.0, and NeoForge only includes that version from build 21.1.195 on. The 1.8.3 changelog says the team moved to 21.1.195 for that reason, while 1.8.2 was still built against 21.1.182. Use 21.1.195 or newer on the server and on every client, and update NeoForge first if your 1.8.2 setup runs an older build.

Both jars accept Java 21 only. The NeoForge file locks the range to Java 21, with a comment that Graal often crashes on newer versions. The Fabric file asks for "java": "21", which Fabric Loader treats as an exact match, so it refuses newer Java versions too. On Fabric you do not add Fabric Language Kotlin yourself, because it ships inside the Cobblemon jar.

Install the loader and runtime required by your chosen pack or loader release. Check that the same runtime is available in the hosting panel before moving an existing world. A newer loader version appearing online is not a reason to replace the version a pack specifies.

For a standalone installation, put the matching Cobblemon file and its required dependency in the server's mods folder. For a modpack, follow the pack's server installation process instead. Cobblemon has to be on the server and on every client; the official modpacks mark it as required on both sides.

Save a complete recovery copy first

Stop the existing server before making the update copy. Keep the world, configuration, mods and startup settings together, with a note of the versions they belong to. Store that copy separately from the directory you plan to change.

Make sure you know how to restore the complete installation. Keeping the old jar alone does not preserve the settings, sidemods or world files from before the update. Tell your group when testing will happen so nobody expects progress on a temporary world to carry over.

Test the update before reopening the world

Use a separate copy of the world for the first start. Read the console output, resolve missing dependency errors and join with a matching client installation. Check that players can connect, their progress loads and the world saves after a restart.

For the 1.8.4 fixes, include the relevant activities in your checks: spawning in affected areas and riding Fearow if your group uses it. Record what you observed. The changelog identifies fixed defects; it does not establish that every sidemod or custom datapack works with the update.

If you are coming straight from 1.8.2, read the 1.8.3 notes as well, because that release from 25 October changed more for servers. It added the doPokemonPredation game rule and a predationChance setting in config/cobblemon/main.json. Together they control how aggressive Pokémon with a hate_entity brain task are and how likely they are to attack their target. The same release fixed a bug in that task, "therefore enabling deadly warfare between Zangoose and Seviper", as the notes put it. By default the game rule is on and the chance is 0.05, according to the 1.8.4 source code; /gamerule doPokemonPredation false stops those attacks.

Version 1.8.3 also added stricter server-side riding checks, made Vikavolt and Fearow rideable and fixed a crash on world load caused by datapacks with item interaction evolutions that do not specify an item.

Choose RAM for the complete installation

The Cobblemon release metadata does not supply a measured RAM minimum or player capacity. A plain installation, a pack with extra dimensions and a public world are different workloads.

Describe your complete mod list, existing world and expected use when comparing plans. During normal play, check memory use and the console before deciding whether the allocation needs to change. Keep enough room for the runtime outside its Java heap, following your host's launch instructions. For a group in India, our Cobblemon guide for players in India sizes the official pack on the Mumbai plans and covers the memory every player's launcher needs.

Check settings and keep a useful problem record

Use the configuration generated by the version you installed. Compare it with that version's documentation before adding keys from an older guide, and change one setting at a time.

If a join or spawning problem remains, record the loader, Cobblemon or pack version, error text and relevant server log. Check sidemods and datapacks as part of the diagnosis. If you use a panel installer, confirm that the exact pack release is listed before relying on it for the move.

FAQ

What is the latest Cobblemon version? As of 28 October 2026 it is Cobblemon 1.8.4, released on 27 October for Minecraft 1.21.1 on Fabric and NeoForge. Modrinth and CurseForge both list it as a release, not a beta. The bigger 1.8.0 update from September is covered in our Cobblemon 1.8 server update guide.

Which Java version does a Cobblemon 1.8.4 server need? Java 21, and only Java 21. The NeoForge jar locks the range to Java 21 and the Fabric jar asks for exactly 21, so a server started on a newer Java version will not load Cobblemon.

Which Fabric or NeoForge version do I need for Cobblemon 1.8.4? On Fabric, Fabric Loader 0.17.2 or newer with Fabric API 0.116.6+1.21.1 or newer. On NeoForge, Kotlin for Forge 5.10 or newer and NeoForge 21.1.195 or newer, the first build that includes the MixinExtras 0.5.0 Cobblemon asks for since 1.8.3. The official 1.8.4 modpacks run Fabric Loader 0.20.1 and NeoForge 21.1.264.

Do I need a new loader when I update from 1.8.2 or 1.8.3? On Fabric, no: the 1.8.4 jar lists the same loader, Fabric API and Java requirements as 1.8.2 and 1.8.3. On NeoForge, only if your build is older than 21.1.195, which is possible on a server that ran 1.8.2. Update the server and every player to 1.8.4 at the same time.

Does Cobblemon 1.8.4 add new server settings? No. Its changelog lists no new config options or game rules. The doPokemonPredation game rule and the predationChance setting arrived in 1.8.3.

Sources

Checked on 28 October 2026: