MCPets

Player-owned modeled pets and mounts built on MythicMobs and ModelEngine: a summon GUI, following AI, mounts, renaming, pet inventories, skins, and a full living pet system with health, experience, levels, taming and evolutions.

Requirements by version

MCPets' dependency floor moves with its major version — the most important version fact about this plugin:

WorldGuard is additionally required if you use the WorldGuard flags.

The three-plugin pipeline

A pet only works if each layer below it already works. Debug in this order — MCPets' own docs are emphatic about it:

1. ModelEngine — drop the .bbmodel into plugins/ModelEngine/blueprints/, run /meg reload, then zip the generated pack from ModelEngine/resource pack/ and apply it client-side.
2. MythicMobs — create the mob that will be the pet, with whatever skills it needs. Verify it standalone: /mm e get <mobName> gives you a spawn egg. The mob and its model must be fully working before MCPets enters the picture.
3. MCPets — add a pet config in plugins/MCPets/Pets/ pointing at that mob, then /mcpets reload.

Cosmetic pet config

Cosmetic pets are invincible — no health, no statistics. Most fields are optional; the minimum is an Id and a MythicMob.

plugins/MCPets/Pets/example.yml

# The unique ID of your pet
Id: your_pet_id
# The mythicmob attached to the pet
MythicMob: the_mythicmob_attached_to_the_pet
# Custom permission to summon your pet
Permission: permission.to.summon.the.pet.can.be.custom

# Mounting: requires a "mount" bone in the ModelEngine model
Mountable: false
MountType: walking
DespawnOnDismount: false
AutoRide: false
MountPermission: mcpets.mount_mypet

# Skill executed on despawn. WARNING: this blocks the auto-remove,
# so end the skill with a 'remove @self' mechanic.
DespawnSkill: DespawnSkill_MM

# Distance before the pet starts returning to its owner
Distance: 10
# Distance within which the pet is summoned
SpawnRange: 1
# Distance within which the pet comes back when too far
ComingBackRange: 3

# Optional carry inventory; rounded up to a multiple of 9
InventorySize: 9

Icon:
  Name: Name of the icon
  Material: STONE
  CustomModelData: 0
  Description:
  - This is a line of description

Signals:
  Values:
  - ATTACK
  - JUMP
  Item:
    GetFromMenu: true
    Name: Signal stick name
    Material: STICK
    CustomModelData: 0

Skins:
  Skin1:
    MythicMob: mythicMobId
    Permission: skin.permission
    Icon:
      Material: STONE
      CustomModelData: 0

The icon may instead use a custom head by supplying TextureBase64 in place of Material.

Living pet config

Living pets are killable and carry health, resistances, experience and levels. Every cosmetic feature still applies — skins, signals, inventories — living pets simply add a Levels block. Experience thresholds drive progression, and at chosen stages a pet can evolve, with permission transfer to the evolved pet handled automatically.

plugins/MCPets/Pets/living_example.yml

Id: your_pet_id
MythicMob: the_mythicmob_attached_to_the_pet
Permission: permission.to.summon.the.pet.can.be.custom
# ... any cosmetic-pet options may also be used ...

Levels:
  Lvl_Beginner:
    Name: "Beginner"
    # XP needed to reach this level. The first level is 0.
    # Levels MUST have different thresholds.
    ExperienceThreshold: 0
    MaxHealth: 200
    # HP regenerated per second, in hearts
    Regeneration: 0.1
    # Division factor on incoming damage (1 = +0%, 2 = +100% resistance)
    ResistanceModifier: 1
    # Multiplication factor on outgoing damage (1 = +0%, 0.5 = -50%)
    DamageModifier: 1
    # Extra placeholder usable in skills to scale skill power
    Power: 1
    Cooldowns:
      # Seconds before the pet can be summoned after dying
      Respawn: 15
      # Seconds before it can be summoned after being revoked
      Revoke: 0
    # Extra inventory slots; rounds up to a multiple of 9
    InventoryExtension: 0

  Lvl_Intermediate:
    Name: "Intermediate"
    ExperienceThreshold: 100
    MaxHealth: 300
    Regeneration: 0.2

Living pets additionally unlock modifiers, taming (with TamingProgressSkill / TamingFinishedSkill hooks) and pet food, configured in petFood.yml with vanilla or custom items for both taming and healing.

Signals & the signal stick

Signals are how a player gives their pet orders. They ride on MythicMobs' signal mechanic, so the behaviour lives in the mob file and MCPets just exposes it:

1. In the MythicMob, add a skill with the trigger ~onSignal:YOUR_SIGNAL_TAG.
2. List YOUR_SIGNAL_TAG under the pet's Signals.Values.
3. Players cycle and cast signals with the signal stick item.

plugins/MythicMobs/Mobs/pet.yml — receiving a signal

MyPetMob:
  Type: WOLF
  Display: 'Companion'
  Health: 40
  Skills:
  - skill{s=PetPounce} ~onSignal:ATTACK
  - jump ~onSignal:JUMP

Mounts

Mountable pets need a mount bone in the ModelEngine model (see bone tags), then Mountable: true in the pet config. MountType selects the mount controller — walking by default. AutoRide mounts the owner on spawn, DespawnOnDismount removes the pet when they get off, and MountPermission gates riding behind a permission node.

MythicMobs additions

With MCPets installed, these become available inside any Mythic skill.

Mechanics

Targeters

Conditions

Placeholders

MCPets also exposes PlaceholderAPI placeholders for use outside Mythic skills.

Plugin config

Selected options from plugins/MCPets/config.yml:

plugins/MCPets/config.yml

# Interaction menu behaviour
EnableClickBackToMenu: true
ActivateBackMenuIcon: true
DismountOnDamaged: true
DisableInventoryWhileHoldingSignalStick: true

# Living-pet respawn behaviour
PercentHealthOnRespawn: 0.2
DefaultRespawnCooldown: 0
# If true, ANY pet is blocked while one cooldown is running
GlobalRespawnCooldown: false
AutoRespawn: false

# Database autosave interval, seconds
AutoSaveDelay: 3600

Experience:
  BarSize: 40
  Symbol: '|'

Taming:
  # CHAT, TITLE or ACTION BAR
  AnnouncementType: CHAT
  BarSize: 40
  Symbol: '|'

# Worlds where pets may not spawn
BlackListedWorlds:
- world_dungeons

# Use flat-file storage instead of MySQL
DisableMySQL: true
MySQL:
  Prefix: myprefix
  User: user
  Password: password
  Host: ip
  Port: 0
  Database: db_name

Commands

Gotchas & common issues

MCPets' documentation carries an unusually large troubleshooting section; these are the failures worth knowing before you hit them:

• Debug in pipeline order. Run /mcpets debug; if the error mentions MYTHICMOBS, the problem is in the mob, not in MCPets.
• Floating horse armor / no model — the ModelEngine model or the resource pack is not applied. Fix at the ModelEngine layer.
• Purple/black textures — a texture or atlas problem in the resource pack; there is a dedicated atlas-issues page, plus a 1.21.4 resource-pack changes page and a guide to merging custom-item packs on 1.21.3 and prior.
• Pet can't be named — the model is missing the tag_name bone (required since ModelEngine r2.3.0).
• Pet can't be mounted — the model is missing the mount bone, or Mountable is false.
• Pet removed or revoked on spawn — usually a protection plugin. For WorldGuard, pets need the region configured to permit them; MCPets provides WorldGuard flags for exactly this.
• Anchor mobs left behind after restart or chunk unload — a documented failure mode with its own page.
• No pet experience — experience is a living pet feature; a cosmetic pet will never gain any.
• Pets missing from a category — category configuration, covered on its own troubleshooting page.

Sources

• MCPets documentation (GitBook)
• MCPets — Requirements
• MCPets — Setup your first pet
• MCPets — Pet features
• MCPets — Pet config templates
• MCPets — MythicMobs add-ons
• MCPets — Common issues
• MCPets source on GitHub