Get Players onto the Cobblemon Server

Getting the server online was only half of the work. The harder support problem was getting every player onto the exact same version of Minecraft, Fabric, Cobblemon, supporting mods, resource packs, and configuration.

The reliable answer is to build one client profile, test it, and distribute that profile as a release. Players should not have to recreate the server owner’s mod research.

What the server owner prepares

Start with a clean Minecraft 1.21.1 Fabric instance in the Modrinth App or Prism Launcher.

Add every mod that affects what the player sees or interacts with:

• Cobblemon and Fabric API
• Trainer and battle additions
• Journey Mounts and Waystones
• Maps
• Backpacks and furniture
• Breeding and outbreaks
• Required libraries and config APIs
• Required resource packs

Leave server-only administration and performance tools out of the client. LuckPerms, VanillaPermissions, and most server performance tools do not belong in a player profile.

That separation matters because unnecessary server mods can crash clients, confuse players, and make updates harder to diagnose.

Test the profile before sharing it

Launch the profile and join a local or staging copy of the server.

Test more than the login screen:

• Create a new player and select a starter.
• Open the map and minimap.
• Find custom terrain and structures.
• Use a Waystone.
• Place custom furniture and storage.
• Start a trainer battle.
• Verify mounts and resource packs.
• Die once and confirm the grave system works.

If a clean profile passes those checks, save it as the release candidate.

Fix shared settings once

Kame House has a keybind conflict on a fresh client. Cobblemon uses M during the starter flow, and Xaero’s World Map also claims M.

Remap the world map to N before exporting the pack. Shared configuration can also include sensible map settings and the required resource-pack order.

Do not include personal data in the exported profile. Remove account information, screenshots, single-player worlds, logs, crash reports, and the private server address unless you explicitly want it distributed inside the pack.

Export the Modrinth pack

In the Modrinth App:

1. Open the tested instance.
2. Go to the Mods tab.
3. Select Export modpack.
4. Include the required mods, configuration, and resource packs.
5. Give the release a clear version such as Kame House 1.0.0.
6. Export the .mrpack file.

The .mrpack format records the Minecraft and Fabric dependencies and tells the launcher where supported files should be downloaded. It is more repeatable than sending a loose folder of JAR files.

Some projects restrict redistribution. Check each project’s permissions before bundling files directly. A manifest that downloads approved files from their original source is preferable.

For a private friend server, share the pack through a private file link or chat. A public Modrinth project is useful later if you want version history and one-click updates, but it also requires proper permissions and project review.

Player installation

Send players these instructions:

1. Install the Modrinth App or Prism Launcher.
2. Import the .mrpack file as a new instance.
3. Sign in with the Microsoft account that owns Minecraft Java Edition.
4. Give the instance roughly 4 to 6 GB of memory.
5. Launch the game once and reach the main menu.
6. Add the server address provided privately by the server owner.
7. Connect and choose a starter.

Cobblemon requires Minecraft Java Edition. Console, mobile, and other Bedrock Edition players cannot use this Fabric client.

Do not update individual mods

Players will occasionally see notices that a newer mod version exists. That does not mean it is compatible with this server.

A map mod may have a newer release for a newer Minecraft version while the server remains on Minecraft 1.21.1. Updating that one file can prevent the client from launching or connecting.

The rule for players is simple: update the whole Kame House pack when a new pack release is provided. Do not update individual mods unless the server owner asks you to test something.

Release updates without creating confusion

When the server changes:

1. Copy the previous client instance.
2. Apply the same compatible mod changes used on the server.
3. Launch and test the copied instance.
4. Export a new versioned .mrpack.
5. Keep the previous pack available during the rollout.
6. Tell players whether the update is required before their next login.

Use release numbers instead of filenames like final, new, or fixed-final. A simple 1.0.0, 1.0.1, and 1.1.0 sequence makes support conversations much clearer.

Troubleshooting order

When a player cannot connect, check these in order:

1. They are using Minecraft Java Edition.
2. They launched the correct Kame House instance.
3. Their pack release matches the server release.
4. They did not update or remove individual mods.
5. The game reaches the main menu without a mod error.
6. The server address was entered correctly.
7. The server is online and the player is allowed to join.

Ask for the launcher log only after checking the version and instance. Most problems are the wrong profile, not a mysterious network failure.

Never ask players to post logs publicly without reviewing them. Logs can contain usernames, local file paths, server addresses, and system details.

Lessons learned

Package the client. Version mismatch is an operations problem, not something every player should solve independently.

Test with a clean account path. An administrator’s existing instance may contain old configs and files that hide missing dependencies.

Ship shared settings. Fixing one keybind in the pack is better than explaining the same conflict to every new player.

Use releases. A named, versioned pack gives everyone a clear answer to “Which files should I have?”

Keep the address private. The client pack can work without publishing the server endpoint on a public project page.

Official references

• Cobblemon installation guide
• Fabric mod installation guide
• Creating a Modrinth modpack
• Sharing private Modrinth packs
• Importing packs with Prism Launcher