Your first NPC¶
This walkthrough creates a simple humanoid trainer, gives it a small battle team, saves a reusable preset, and spawns a second copy. Use a disposable creative world while learning.
1. Obtain the tools¶
Run as an operator or a builder with the required permissions:
Right-click a clear block with the Humanoid NPC Egg. A humanoid appears next to the clicked block face. Egg-created characters initially have battles disabled and use dialogue interaction.
2. Name and position the trainer¶
Right-click the character with Edit NPC. Set Name to a name such as Town Trainer. Save it.
Use Move Wand if the character is not standing where you want it:
- Right-click the character with the wand.
- Right-click its destination block.
- Successful movement updates its home and clears the selection.
Open the editor again. Appearance, body pose, skin source, and equipment are optional for the first battle; the default humanoid is enough to test the workflow.
3. Build a battle team¶
Open the Team section and its team editor. Add one Pokémon and configure a simple example:
| Field | Example |
|---|---|
| Species | pidgey |
| Level | 5 |
| Move 1 | tackle |
| Form | Empty/default |
| Shiny | Off |
The team editor supports up to six Pokémon. Use suggestions to select valid species, moves, abilities, and other registered values. For this first NPC, keep the team local to the character rather than overwriting a shared team file. A file-write option can appear when you are editing a team sourced from a file and have file-edit permission.
Apply the team editor and save the main NPC editor. Closing a nested editor without applying its changes does not produce a completed saved trainer.
4. Enable the battle interaction¶
In the NPC editor:
- Enable the trainer's battle setting in the Battle section.
- Set On Interaction to
battlein Interaction. - Use the normal level mode and a single battle for the first test.
- Leave One Battle per Player off and the rematch cooldown at zero while testing.
- Save.
The trainer team and the visual appearance are separate. A humanoid can use any valid configured Pokémon party. Likewise, changing a Pokémon NPC's appearance does not automatically build its battle party.
5. Test with your player party¶
Obtain a Pokémon through your installed Cobblemon setup and ensure it can battle. Use Cobblemon's normal starter/party tools for your instance. An empty or fully fainted party cannot start this trainer battle.
Put away administrative tools and right-click the NPC. The server checks battle access, prerequisites, party requirements, attempt limits, and cooldowns before starting.
If no battle starts, reopen the editor and check:
- Battle is enabled.
- On Interaction is
battle. - The team has at least one valid Pokémon.
- Your player party is healthy and satisfies the configured size/level limits.
- You have not enabled a tag, permission, prerequisite, or attempt limit that blocks the test.
6. Export your own preset¶
Stand within 8 blocks and look directly at the trainer, then run:
Export names use lowercase letters, digits, _, -, and / for folders. This creates:
If the character has a nonempty inline team, export writes that team separately to:
The exported preset references the team file and is reloaded. The placed NPC is assigned to that saved trainer ID. Existing files are protected unless you deliberately add overwrite:
Choose the final preset identity before inviting players to progression battles. Battle history is keyed by the player and trainer ID, not just by the placed entity's UUID. Changing identity later can change which history record is used.
7. Spawn another copy¶
Move to another clear location and run:
The two placed NPCs have distinct entity UUIDs but share the trainer preset identity. Player progression against that trainer can therefore be shared between its copies. Use a different trainer preset ID when you need a genuinely separate progression encounter.
Next, explore concepts, presets, appearance, and the administrative tools.