How to install pre-made Model Engine + MythicMobs packages

Step 1: Understanding the files you’ve downloaded (skip if you just want to install and not learn)

Most likely the vendor that has sold you or given you this package has given you 2 folders “MythicMobs” and “ModelEngine”.

One folder contnains the Model Engine files and one folder is the MythicMobs files. Sometimes they even come as a big folder with them all in the same place, here is what you need and what each file does:

• .bbmodel file
  • This file is used by ModelEngine and contains model, texture and animations. ModelEngine will autmatically create your resource pack from this file.
• Alternatively if there is no .bbmodel file you will get 3 files from a Bedrock project: 1 .json file, 1 .png file and 1 .animation.json file.

• Mobs .yml text file
  • This file is used by MythicMobs as the foundation to your mob/mobs.
  • You can learn more about mob options in MythicMobs here, on their official wiki.
• Skills .yml text file
  • This file is used to define all the skills and abilities of the mob/mobs (and sometimes custom items) in MythicMobs.
  • Learn more: MythicMobs Skills wiki.
• Droptables .yml text file (Optional and not always used or included).
  • This file contains drop or loot tables for mobs, usually used when you need more advanced systems then the default mob .yml can handle on its own.
  • Learn more: MythicMobs Drops and Droptables wiki.
• Items .yml text file (Optional and not always used or included).
  • This file is used to create and define custom items in MythicMobs.
  • Learn more: MythicMobs Items wiki.
• randomspawns .yml text file (optional and not always used or included).
  • This file is used to make your custom mob/mobs spawn automatically in the world.
  • Learn more: MythicMobs Random Spawns wiki.

• sound assets and sounds.json (optional and comes in more advanced packages)
  • These files make it so we can have custom sounds for the mob/mobs.

Step 2: Import the file/files to ModelEngine

1. Put your .bbmodel file inside the blueprints folder located at: plugins/ModelEngine/blueprints
2. If you never got a .bbmodel file please import the other files accordingly:
   • .json goes into plugins/ModelEngine/blueprints
     • Sometimes your .json might be called .geo.json, please remove the .geo so it’s only called .json
   • .png goes into plugins/ModelEngine/resource pack/assets/modelengine/textures/entity
   • .animation.json into plugins/ModelEngine/animations

Now reload the plugin using /meg reload models

Step 3: Export the resource pack files that ModelEngine made for you.

Only do 3.1 or 3.2, not both.

Step 3.1: If you want to use the Resource Pack you already have + ModelEngine files.

Copy this folder: plugins/ModelEngine/resource pack/assets/modelengine
And put it into your current Resource pack here: YourPack/assets/modelengine

Then copy over the plugins/ModelEngine/resource pack/assets/minecraft/models/item/leather_horse_armor.json file
And put it into your current Resource Pack here: YourPack/assets/minecraft/models/item/leather_horse_armor.json

Now you can use your old resource pack with the servers ModelEngine models.

Step 3.2: If you want to make your own resource pack.

Copy and rename the folder plugins/ModelEngine/resource pack
This folder contains everything you need from ModelEngine to make a resource pack.

Now put your pack.mcmeta file inside that folder, and your new resource pack is done!
If you need a new pack.mcmeta file you can create this file by making a text file named so containing:

{
  "pack": {
    "pack_format": X,
    "description": "MC Models is the best"
  }
}

Replace the X for pack_format with the number for the game version you are using:

• Minecraft 1.13 – 1.14.4 has “pack_format”: 4,
• Minecraft 1.15 – 1.16.1 has “pack_format”: 5,
• Minecraft 1.16.2 – 1.16.5 has “pack_format”: 6,
• Minecraft 1.17 and up has “pack_format”: 7,

Here are some pre-made pack.mcmeta we’ve made for you:

Put your new resource pack folder, that you renamed, inside the resource pack folder that you find from the in-game Minecraft settings.

If you need to merge this resource pack with your own one, please refer to our “How to marge resource packs” tutorial (Coming soon).

Step 3.3: Sounds

If your package comes with custom sounds you should add these to the resource pack you just made.

• sounds.json
  • This file goes into your resource pack here (unless instructed otherwise): YourPack/assets/minecraft/sounds.json
• The sound files can go in many places in the resource pack, follow your specific package instruction or open the sounds.json with a text editor and see where they are specified to be.

Step 4: Import the MythicMobs .yml files.

It’s quite easy to undestand where MythicMobs files go, this is what the plugins/MythicMobs folder looks like:

Now put the files in the correct folders, one by one.

• Mob yml goes into the Mobs folder.
• Items yml goes into the Items folder.
• DropTables yml goes into the DropTables folder
• RandomSpawns yml goes into the RandomSpawns folder
  • Make sure its not the Spawners folder you put it into, this is a mistake I’ve seen many do.
• Skills yml goes into the Skills folder

Once done, reload MythicMobs using /mythicmobs reload

Step 5: Enjoy

Now load up your new resource pack and spawn in the mobs using MythicMobs command:

/mythicmobs m spawn [Internal_Mob_Name]

Quite easy, the command is tab completed.