The Mythic suite

Six server plugins — MythicMobs, ModelEngine, MythicCrucible, MythicDungeons, MythicArmors and MCPets — that together cover custom mobs, 3D models, items, instanced dungeons, wearable armor and pets. This hub explains how they stack, which versions go together, and where each one's reference page lives.

📌 Scope note

These are server plugins (Paper/Spigot), not data packs. Their content is authored in YAML under plugins/, not JSON under data/, and none of it loads on a vanilla client-only setup. They earn a place in this codex because they solve the same problems data packs do — custom mobs, loot, items, worldgen decoration — and because they interoperate with pack-side work: Crucible and MythicArmors generate resource packs, and Mythic items are given with vanilla data components such as minecraft:equippable. Everything below is plugin-side unless it explicitly says otherwise.

On this page

How the six plugins stack
The reference pages
Version & compatibility matrix
Free vs premium
Packs: the shared content unit
Interoperation & known conflicts
Sources

How the six plugins stack

MythicMobs is the foundation. It owns the entity model, the YAML skill system (mechanics, targeters, triggers, conditions), items, drop tables, spawners and stats. Every other plugin here either extends that skill system with new mechanics or consumes it.

Plugin	Layer	Depends on	What it adds
MythicMobs	Core	—	Mobs, skills, items, drops, spawners, stats. The scripting language the rest speak.
ModelEngine	Presentation	Standalone (integrates with Mythic)	Server-side 3D models & animation from Blockbench, with no client mod. Adds model/bone/mount mechanics.
MythicCrucible	Content	MythicMobs	Custom items, armor sets, blocks, furniture, recipes, augments — plus resource-pack generation.
MythicDungeons	Content	Standalone; deeply integrates MythicMobs	Instanced, scripted dungeon worlds with their own functions, triggers and conditions.
MythicArmors	Presentation	Standalone (integrates with Mythic/Nexo)	Wearable 3D armor via resource-pack core shaders.
MCPets	Content (third-party)	MythicMobs and ModelEngine	Player-owned pets & mounts: GUI, taming, levelling, inventories, skins.

MCPets is the only one here not published by MythicCraft — it is a third-party plugin built on top of two of them, documented on its own GitBook.

The reference pages

MythicMobs — mob options, the skill line anatomy, and the full mechanic / targeter / trigger / condition indexes.
ModelEngine — bones vs cubes, importing models, the meg mechanic families, mounts and configuration.
MythicCrucible — item types and options, furniture, custom blocks, recipes and the resource-pack generator.
MythicDungeons — dungeon config, functions, triggers, conditions and the Mythic integration surface.
MythicArmors — the Blockbench bone contract, tint/emissive/fallback textures, and giving armor via vanilla, Crucible or Nexo.
MCPets — pet config, living pets, signals, mounts, and its MythicMobs mechanic/targeter/placeholder additions.

Version & compatibility matrix

Mythic plugins are versioned per-plugin, not as a suite — but Crucible tracks MythicMobs' version number, which is why Crucible jumped from the 2.x line straight to 5.x. A matched set is the safe default.

Plugin	Current line	Notes on the numbering
MythicMobs	5.13.x	Free and Premium builds share the version number; Premium ships as `MythicMobsPremium-<ver>`.
MythicCrucible	5.13.x	Deliberately mirrors the MythicMobs version it targets. Pre-5.x builds used an independent 1.x/2.x line.
ModelEngine	R4.1.x	Uses an `R`-prefixed release series (R2 → R3 → R4), not semver-aligned with Mythic.
MythicDungeons	2.0.x	2.0 is a major rewrite that also introduces the free-tier procedural limits.
MythicArmors	see note	Its wiki carries no changelog; the meaningful axis is the Minecraft version (below), not a plugin version.
MCPets	4.1.x	Dependency floor moves with the major: 4.1.0+ needs ModelEngine r4+.

⚠ Version differences

MCPets → ModelEngine floor — MCPets 4.1.0+ requires ModelEngine r4+; 2.0.1–4.0.4 require r3+; 2.0.0 and older require r2+. All MCPets versions require MythicMobs 5.0.0+, and LuckPerms for some features (e.g. evolutions).
MCPets pet name tags — since ModelEngine r2.3.0 you must supply your own name-tag bone; MCPets standardises on a bone named tag_name.
MythicArmors on macOS — from MC 1.21.6 through 26.1, macOS is limited to OpenGL 4.1 and cannot run the 3D core shader, so a 2D fallback renders instead. From 26.2, macOS on Vulkan gets the full 3D armor.
MythicArmors reduced-draw-calls — the experimental four-faces-per-texture packing requires 26.2+ and breaks armor rendering on 1.21.6 → 26.1. Leave it false unless the whole player base is on 26.2+.
MythicDungeons 2.0.1 — adds Paper 1.21.1–1.21.4 support, with 1.21.5 flagged experimental by the changelog.
MythicArmors requires Java 25 on Paper-based servers — stricter than the rest of the suite, and a common reason it alone fails to load.

💡 Best practice

Pin a known-good set and upgrade it as a unit. A set verified together against Paper 26.2 is MythicMobsPremium 5.13.1 + MythicCrucible 5.13.0 + ModelEngine R4.1.1 + MythicDungeons 2.0.1. Upgrading MythicMobs alone while leaving Crucible on an older minor is the usual cause of "mechanic not found" errors after an update, because Crucible registers mechanics against the core it was built for.

Free vs premium

Free	Premium (paid)
MythicMobs, ModelEngine 4, MythicAchievements, MythicCosmetics, MythicDungeons	MythicArmors, MythicCrucible, MythicEnchantments, MythicHUD, MythicRPG

MythicMobs itself is free, but has a Premium tier that unlocks capabilities used pervasively in advanced configs. Those unlocks apply across the other Mythic plugins too — buying MythicMobs Premium changes what you can write in Crucible, Dungeons and the rest:

Placeholders and Math inside mob attributes, item attributes, most skills, and drop-table amounts.
Skill parameters, in-line target conditions, and conditional AI goals/targeters.
origin=@targeter in any mechanic; on-hit conditions and bounce in projectile skills.
Custom damage types and damage modifiers.
Premium-only mechanics including raytrace and chainmissile.

MythicDungeons' free version allows 2 dungeons, and from 2.0 restricts procedural dungeons to 1 dungeon, 15 rooms, 5 unique rooms. Non-procedural dungeons have no feature locks.

Packs: the shared content unit

MythicMobs "packs" bundle related content into one self-contained folder, and the sibling plugins read out of the same tree. This is the cleanest way to ship a themed content set:

plugins/MythicMobs/packs/<YourPack>/

packinfo.yml        # pack metadata + dependency gating
mobs/               # mob definitions
skills/             # metaskills
items/              # items (Crucible extends these)
drops/              # drop tables
models/             # .bbmodel files -> read by ModelEngine
armors/             # .bbmodel files -> read by MythicArmors

🎩 Trick

5.13.0 packinfo.yml gained PackDependencies and FileDependencies. Declaring them makes Mythic skip content gated behind a missing plugin instead of parsing it and spraying errors into console — which is what lets one pack ship optional Crucible or Enchantments content safely:

plugins/MythicMobs/packs/<YourPack>/packinfo.yml

PackDependencies:
- MythicCrucible
FileDependencies:
- enchantments/* MythicEnchants

Interoperation & known conflicts

🚧 MythicArmors ✕ ModelEngine shaders

MythicArmors renders 3D armor with resource-pack core shaders, and is incompatible with other entity core shaders — including the one ModelEngine generates. If you run both, set create-shader: false in plugins/ModelEngine/config.yml. MythicArmors' own docs give this as the fix, and add a vendor rule: a distributed pack should tell the user to change that value, never ship a modified ModelEngine config.

⚠ Gotcha — mechanic name collisions

Two addons can register the same mechanic name; the later registration wins and your skill silently does the wrong thing. Disambiguate with the addon's namespace prefix. ModelEngine documents exactly this case against Crucible:

plugins/MythicMobs/skills/example.yml

Skills:
# The Crucible mechanic
- setitemmodel{m=3} @self

# The Model Engine mechanic, namespaced
- meg:setitemmodel{mid=testmodel;bone=examplebone;i=STONE} @self

Other integration points worth knowing:

MythicArmors → Crucible / Nexo — MythicArmors can register its armor as MythicMobs/Crucible items (<namespace>:<set>_<piece>) or as Nexo items, and can hand its assets to either pack generator instead of emitting its own pack.zip.
Crucible → external packs 5.13.0 — the generator can merge external resource packs from local paths or URLs, with explicit ordering.
MCPets → MythicMobs — MCPets drives pets through Mythic's signal mechanic and adds its own mechanics (givePet, petFollow, …), targeters (@PetOwner, @PetFromOwner), conditions and <pet.*> placeholders.
MythicDungeons → MythicMobs — dungeons expose their own mechanics, conditions, targeters, triggers, variables and placeholders to Mythic skills, so a boss skill can query dungeon state.