Configure a Cobblemon server only after it completes a successful first start. Stop it cleanly, back up the world, config, mods and server properties, then change a small group of settings. Restart and test login, spawning, capture, battle and persistence before allowing players in.
Requirements and version covered
This guide covers Cobblemon 1.7 on Minecraft Java 1.21.1 with Fabric or NeoForge. Names were checked against official source and release notes on August 17, 2026. If the server is not running yet, first host and install a Cobblemon server and choose a compatible loader and version.
Back up before changing settings
- Notify players and prevent new logins.
- Save the world, then stop the Java process cleanly.
- Copy the world directory,
config,mods,server.properties, access lists and launch scripts. - Store the copy outside the active instance and record versions and date.
- Open the archive once before making changes.
Test with a clean client instance
Create a separate client profile with the same Minecraft version, loader and required mods. A personal profile full of extras may hide missing dependencies during the first test.
Where Cobblemon server config files are stored
| File or folder | Role | Scope | Restart | Risk |
|---|---|---|---|---|
server.properties |
Difficulty, game mode, network | Server | Usually | Medium |
config/cobblemon/main.json |
Main Cobblemon settings | Instance | Varies, restart is safest | High |
| World directory | World and player data | World | Stop before backup | Very high |
mods |
Cobblemon, loader and extensions | Client/server by mod | Yes | High |
| Operator and access lists | Vanilla permissions | Server | Command-dependent | High |
Minecraft, loader and Cobblemon files
server.properties belongs to Minecraft. Cobblemon 1.7 stores its main configuration at config/cobblemon/main.json. The official changelog documents /cobblemonconfig reload while warning that some options require a restart. Other mods have their own locations, so follow their documentation.
Global settings and per-world settings
Separate instance configuration, world data and datapack behavior. A copy of main.json cannot restore player data. A world-only backup cannot restore the matching mod list.
Essential settings before opening the server
Difficulty, game mode and permissions
Set difficulty, default mode, whitelist, operators and network exposure. Grant administration to named accounts, then test with a non-operator account so elevated permissions do not hide failures.
Pokémon spawns and behavior
Cobblemon’s main file exposes global settings including spawning controls and shinyRate. Do not paste an old configuration over a new version without comparison. Change one value at a time, validate the JSON, and observe several areas and dimensions. Low spawns may also come from Minecraft limits or another mod.
Client and server mod compatibility
Each project should state whether it is needed on the server, client, or both. Keep Cobblemon and shared gameplay components aligned with the tested pack. Some visual mods are client-only, but verify that in their documentation. Review compatible complementary mods before expanding the pack.
Backups, updates and rollback
Pre-update checklist
- Read release notes for Cobblemon, the loader and every addon.
- Clone the instance and restore the world backup on a test server.
- Compare newly generated configuration files with the old ones.
- Test login, capture, battle and restart.
- Keep the previous pack and Java runtime until validation is complete.
Restore a stable configuration
Stop the server, preserve the failed instance for diagnosis, and restore the world, mods and configs from the same backup set. Test privately. Mixing a newer world with older mods may worsen a failure.
How to test your settings
Login, capture, battle and restart checks
Test a new player and an existing player. Check dimension travel, spawns, capture, sending and recalling a Pokémon, battle, PC storage and saving. Restart and confirm teams, inventories and settings persist. Read server logs even when the client shows no error.
Technical sources checked August 17, 2026: Cobblemon 1.7 configuration source and official 1.7 changelog.
FAQ
Must the server restart after every change?
Not always, because 1.7 provides a reload command. Some options still require a restart, and a controlled restart remains the safest public-server validation.
Which mods are required on the client?
Every mod whose author marks it client-side or both-sided. Distribute a tested manifest instead of a hand-copied list.
How can you prevent world corruption?
Stop cleanly, keep backups outside the active instance, test updates on copies, and restore matching sets of world, mods and configuration.