Cobblemon commands are mainly used to administer, diagnose or test a game. They are not required for normal play, and the official documentation states that they require commands to be enabled or sufficient permissions. On a public server, always start with a backup and test with a non-operator account. A command capable of creating, modifying or deleting a Pokémon should never be entrusted to an ordinary role.
Before running a Cobblemon command
In a single-player game, access depends on whether commands are enabled. On a server, it depends on the operator level and any permission system added to the modpack. The “unknown command” message can therefore mean that Cobblemon is not loaded, that the command does not exist in this version or that the player does not have permission to see it.
Start with /cobblemon info. The official documentation identifies it as the command that displays version information. It helps confirm that the client, server and guide you are reading all refer to the same branch. To prepare an instance correctly, also see the Cobblemon installation guide and the essential Cobblemon server settings.
Before using a command that affects a player’s data:
- stop any automated operations that could modify the same team;
- back up the world and player data;
- copy the username, target and slot number exactly;
- try the syntax on a test server with a Pokémon of no value;
- then check the team, PC and persistence after restarting.
Useful commands for healing, checking and storing
/healpokemon [target], also documented with the /pokeheal alias, heals the target’s team. If the target is omitted, the behavior depends on the syntax accepted by the installed version. Use autocomplete rather than guessing. To play without privileges, a Healing Machine remains the normal solution, detailed in our guide to healing your Pokémon in Cobblemon.
/pc opens the PC of the user running the command. This administrative option does not mean that a server should offer it to everyone. Remote access can alter the balance of an adventure or make community-built infrastructure pointless.
/friendship <slot> displays the friendship of the Pokémon in the specified slot. The first slot is 1. This command is useful for diagnosing a friendship-based evolution without directly modifying the creature.
/pokebox <target> <slot> [box] sends a Pokémon from the team to a PC box. Double-check the target and box number. The documentation also lists /pokeboxall, which stores an entire team. A selection error can move more Pokémon than intended.
Creation and modification commands
/spawnpokemon <species> [properties], aliased as /pokespawn, spawns a creature at the command user’s position. The English names in angle brackets are the two parameters from the official syntax. The official example combines a species with properties, such as a shiny appearance or an ability. Accepted properties may change: copy verified syntax from the documentation for your version and do not grant this permission to players.
/givepokemon <species> [properties], aliased as /pokegive, adds a Pokémon to the user. /givepokemonother <target> <species> [properties] targets another player. These commands bypass capture and are therefore not a normal progression method. On The Tower, capture is never limited, but that does not grant access to generation commands.
/pokemonedit <slot> [species / properties], aliased as /pokeedit, modifies a Pokémon on the team. These labels correspond to command parameters, not values to enter literally. The /pokemoneditother variant acts on the specified target. Reserve them for documented corrections or a test environment. For a public event, record who requested the correction, the value before the intervention and the resulting value.
/teach <target> <slot> <move> teaches a compatible move according to the official syntax. /levelup <target> <slot> raises the selected Pokémon by one level. Both commands directly affect progression and must be treated as administration tools, not gameplay tips.
Diagnosing spawns and battles
/checkspawn <rarity> checks the spawn chance associated with a rarity at the command user’s exact position. The result depends on the location, spawn context and configuration. It does not promise an encounter and does not replace observing the server for a sufficient period.
/spawnpokemonfrompool [number] asks the system to spawn one or more Pokémon from the local pool. The documentation states that the operation may fail if it violates configured spawn limits and that it cannot be run remotely. It is a targeted diagnostic tool, not a command to repeat continuously.
/stopbattle <target> stops the targeted player’s battle. Use it only to resolve a confirmed lockup, because it interrupts the current state instead of identifying its cause. Keep the logs and mod versions before repeating the test.
Destructive commands that must be protected
The official documentation warns that /clearparty <target> completely clears the team, while /clearpc <target> clears the PC. /pokemonrestart resets the user’s team and PC; /pokemonrestartother <target> applies this reset to the target. These commands do not necessarily require an additional confirmation.
Never try them “just to see.” Restrict their permission, back up before any intervention and request written confirmation for the correct account. If the goal is only to move a creature, use a command limited to the correct slot. An untested backup is not a reliable rollback.
Sources consulted on September 2, 2026: the official Cobblemon command list, which provides syntax, aliases and warnings, and the official Cobblemon 1.7.0 notes, which notably document commands and settings added in this branch.
FAQ
Why is a Cobblemon command unknown?
Check that the server loads Cobblemon, that your client uses the same modpack, that the command exists in the installed version and that your account has the necessary permissions. Autocomplete often helps distinguish incorrect syntax from a missing permission.
Do players need commands to progress?
No. The commands documented here are primarily testing and administration tools. Capture, healing, storage and progression all have normal in-game mechanics.
Can a command reverse permadeath?
That is not a gameplay rule. On The Tower, permadeath occurs only in the Tower and during raids, nowhere else. Any potential administrative intervention is governed by a server procedure, not a freely accessible command.