Skip to content
Skills Library
Programming · Building & coding

create-mob

/create-mob

Create a new mob (custom entity) for a Minecraft Bedrock Edition add-on from a plain description, or change an existing one, including its health, attacks, AI behavior, taming, riding, drops, and natural spawning. Use this whenever someone wants a new creature, monster, animal, pet, boss, or NPC, or wants to change how one of their mobs behaves, for example "make a rideable red panda", "add a goblin that spawns in swamps at night", "make my goblin scared of zombies", or "give the goblin more health". For items use create-item, for blocks use create-block, and for changing how a mob looks use d

Licence
MIT
Last repository change
06.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
5
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Create a new mob (custom entity) for a Minecraft Bedrock Edition add-on from a plain description, or change an existing one, including its health, attacks, AI behavior, taming, riding, drops, and natural spawning. Use this whenever someone wants a new creature, monster, animal, pet, boss, or NPC, or wants to change how one of their mobs behaves, for example "make a rideable red panda", "add a goblin that spawns in swamps at night", "make my goblin scared of zombies", or "give the goblin more health". For items use create-item, for blocks use create-block, and for changing how a mob looks use d

Triggers from the description

make a rideable red pandaadd a goblin that spawns in swamps at nightmake my goblin scared of zombiesgive the goblin more health
Original author description

Create a new mob (custom entity) for a Minecraft Bedrock Edition add-on from a plain description, or change an existing one, including its health, attacks, AI behavior, taming, riding, drops, and natural spawning. Use this whenever someone wants a new creature, monster, animal, pet, boss, or NPC, or wants to change how one of their mobs behaves, for example "make a rideable red panda", "add a goblin that spawns in swamps at night", "make my goblin scared of zombies", or "give the goblin more health". For items use create-item, for blocks use create-block, and for changing how a mob looks use d

How it works

  1. 1. Understand the request
  2. 2. Pick the project folder and namespace
  3. 3. Generate with createMinecraftContent
  4. 4. Check what was generated
  5. 5. Give it a readable name
  6. 6. Make it look right
  7. 7. Validate
  8. 8. Tell the user
  9. Changing an existing mob
  10. If the MCP tools aren't available
Original SKILL.md headings · 100 lines, 1,120 words
SKILL.md preview
---
name: create-mob
description: Create a new mob (custom entity) for a Minecraft Bedrock Edition add-on from a plain description, or change an existing one, including its health, attacks, AI behavior, taming, riding, drops, and natural spawning. Use this whenever someone wants a new creature, monster, animal, pet, boss, or NPC, or wants to change how one of their mobs behaves, for example "make a rideable red panda", "add a goblin that spawns in swamps at night", "make my goblin scared of zombies", or "give the goblin more health". For items use create-item, for blocks use create-block, and for changing how a mob looks use design-model. Not for Minecraft Java Edition mods.
---

# Create or change a mob

A working mob spans several files across two packs: the behavior pack entity, a client entity, geometry, texture, render controller, and optionally a loot table and spawn rule. For a new mob, the Minecraft Creator Tools MCP tool `createMinecraftContent` writes all of them in one call; your job is to translate the request into its definition, then check and finish what it produces. For a mob that already exists, skip to "Changing an existing mob".

## 1. Understand the request

Work out, or choose sensible defaults for:

- Name and a short lowercase ID (`swamp_goblin`).
- Attitude: hostile, neutral, or passive. How it fights, if at all.
- Size and rough look (body type, colors).
- Special behaviors: tameable, rideable, breedable, flies, swims, avoids or hunts certain mobs.
- Drops, and where and when it spawns (or summon-only).

Only ask the user when an answer would change the design a lot. Otherwise pick defaults and say what you chose at the end.

## 2. Pick the project folder and namespace

- Existing project (has `behavior_packs/`): reuse its namespace. Look at the `identifier` values in existing files (`goblins:...`).
- New project: use an empty folder and a short lowercase namespace made of letters, digits, and underscores, such as the creator's name or the add-on's theme. Never use `minecraft`.

## 3. Generate with `createMinecraftContent`

Pass `outputPath` as the project folder itself; don't add a subfolder. The tool's input schema lists every field, and `references/behaviors.md` maps common requests to traits, behavior presets, and native components.

A typical entity entry:

```json
{
  "id": "swamp_goblin",
  "displayName": "Swamp Goblin",
  "traits": ["humanoid", "hostile", "melee_attacker"],
  "behaviors": ["wander", "hide_from_sun", "look_at_player"],
  "health": 16,
  "attackDamage": 3,
  "scale": 0.5,
  "families": ["goblin", "monster"],
  "appearance": {
    "primaryColor": "#4F7A3A",
    "secondaryColor": "#6B4E2E",
    "textureStyle": "organic",
    "eyes": "glowing"
  },
  "drops": [{ "item": "minecraft:brown_mushroom", "count": { "min": 1, "max": 2 } }],
  "spawning": { "biomes": ["swamp"], "lightLevel": { "max": 7 }, "weight": 20, "groupSize": { "min": 1, "max": 3 } }
}
```

Use `components` for anything traits don't cover; they're native Minecraft components and override trait defaults.

## 4. Check what was generated

The generator doesn't report everything it skipped, so open the files and compare them with the request. Known gaps as of Creator Tools 0.17:

- **Unknown fields are silently dropped.** If a value you passed isn't in the output, check the field name against the tool's input schema.
- **The summary can say "0 loot tables / 0 spawn rules"** even when inline `drops` and `spawning` created them. Trust the files, not the summary.
- **`drops[].chance` isn't applied.** Add a condition to the entry in `loot_tables/entities/<id>.json`: `"conditions": [{ "condition": "random_chance", "chance": 0.3 }]`. For player-kill-only drops add `{ "condition": "killed_by_player" }`.
- **`spawning.timeOfDay` isn't applied.** For night or dark-only spawning use `"lightLevel": { "max": 7 }`, which produces a `minecraft:brightness_filter`.
- **`population_control` is always `animal`.** Change it to `monster` in `spawn_rules/<id>.json` for hostile mobs, or `water_animal` for aquatic ones, so they share the right mob cap.
- **Adding to an existing project rewrites both manifests.** The behavior pack's dependency on its resource pack gets a new UUID that points at nothing, and `header.name` is reset. Check `git diff` (or compare with a copy you made first) and restore the original manifest values. The debug-addon validation script reports a broken dependency as `[PACKDEP]`.
- **`tameable`, `rideable`, and `breedable` configuration objects are ignored.** The traits always use bones to tame, wheat to breed, and a saddle to ride. Edit the generated `minecraft:tameable`, `minecraft:breedable`, and `minecraft:rideable` components as described in `references/behaviors.md`.
- **Trait component groups can override your components.** For example, the `hostile` trait adds a `hostile_angry` group with its own `minecraft:behavior.nearest_attackable_target` (targeting players) when the mob spawns, replacing a targeting component you put in `components`. Merge your targets into the group's `entity_types` list instead of defining the component twice.

## 5. Give it a readable name

Creator Tools doesn't create localization, so in game the mob shows as `entity.<namespace>:<id>.name`. Run the debug-addon skill's names script, passing the display name the user asked for. `<debug-addon-skill-folder>` is the debug-addon skill's folder, next to this skill's folder; if it's missing, install the debug-addon skill too.

```bash
node "<debug-addon-skill-folder>/scripts/add-missing-names.mjs" <project-folder> --name "swampy:swamp_goblin=Swamp Goblin"
```

It writes `entity.swampy:swamp_goblin.name` and the spawn egg name to `resource_packs/<pack>/texts/en_US.lang`, creating the file if needed.

## 6. Make it look right

The default geometry is a generic body for the chosen type, with a generated texture. If the user described a specific look, use the design-model skill with `modelId` set to the mob's ID. Afterwards, make sure `geometry.default` in `resource_packs/<pack>/entity/<id>.entity.json` matches the new `.geo.json` identifier; otherwise the mob is invisible.

## 7. Validate

Follow the debug-addon skill: run its validation script, add pack icons (new projects don't have them), and fix errors until none remain.

## 8. Tell the user

Summarize the files created, the defaults you picked, and anything you couldn't do. Explain how to try it: enable both packs on a world with cheats on, then use `/summon <namespace>:<id>` or the spawn egg from the creative inventory. To look at it without Minecraft, they can run `npx -y @minecraft/creator-tools@latest view -i <project-folder>`.

## Changing an existing mob

Most requests in an existing project are changes: "more health", "make it scared of zombies", "tame it with fish instead". If the mob is a vanilla one (such as `minecraft:wolf`) that isn't in the project, say that changing vanilla mobs isn't covered by these skills yet, and offer to make a custom mob based on it instead.

1. Find the mob's behavior pack file (`behavior_packs/<pack>/entities/*.json`, matched by `identifier`). For a quick overview of what it already does, `getEffectiveContentSchema` on the project folder summarizes each mob as traits and properties.
2. Edit the JSON directly. Running `createMinecraftContent` again won't help: it leaves files that already exist untouched, so new values never reach the mob.
3. Look at `components`, then `component_groups` and `events`. A component in an active group replaces the one of the same name in `components`, so change it where it's actually in effect. `references/behaviors.md` has native components for common requests (targeting, fleeing, protecting the owner).
4. Keep `priority` values sensible: lower numbers win, so a "flee" behavior must have a lower number than "wander" to interrupt it.
5. Validate with the debug-addon skill, and tell the user what changed and how to see it in game.

## If the MCP tools aren't available

This skill needs the Minecraft Creator Tools MCP server (`npx -y @minecraft/creator-tools@latest mcp`). If its tools are missing, tell the user and suggest adding that server. As a fallback, `npx -y @minecraft/creator-tools@latest add --help` lists template-based commands; these need the user to have accepted the Minecraft EULA themselves (`npx -y @minecraft/creator-tools@latest eula`). Never accept it on their behalf.
Files in this package (5)
  • SKILL.md 8 KB
  • agents/openai.yaml 1 KB
  • assets/icon-small.png 1 KB
  • assets/icon.png 3 KB
  • references/behaviors.md 7 KB

Versions

The database has no other skills named create-mob.

Database snapshot: 13.11.2026 · package version 38609a5db7ec (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90ro-create-mob
    Design and implement a custom monster or boss for rAthena - role and stats, mob database entry, drops, skills/AI, spawns, client sprite. Use when the user says "create a monster", "add a boss / MVP / mini-boss", "new mob", "change where monsters spawn", or "design a hunting ground".
  • 100create-item
    Create a new item for a Minecraft Bedrock Edition add-on from a plain description, or change an existing one, such as a weapon, tool, food, armor piece, throwable, or collectible, including its icon and crafting recipe. Use this whenever someone wants a new item or wants to…
  • 100create-block
    Create a new placeable block for a Minecraft Bedrock Edition add-on from a plain description, or change an existing one, such as a decorative, glowing, ore, crate, slab, stairs, or light-source block, including its texture, sounds, mining time, drops, which way it faces, and…
  • 90mc-entities
    Create or change entities and mob behavior in a Fabric or NeoForge mod: custom mobs, AI goals, brains, attributes, spawning, renderers and models. Use for "add a mob", "make X follow/attack/flee", or changes to how vanilla mobs behave.
  • 100add-custom-mob
    Use when adding new mobs or entities. Covers entity class, model, renderer, client registration, spawn config, loot tables.
  • 100minewright-project
    Set up and package a Minecraft Bedrock add-on project: behavior pack and resource pack folders, manifest.json format_version 2 with fresh UUIDs, min_engine_version, script module dependencies on @minecraft/server and @minecraft/server-ui by version string, a TypeScript build…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.