Packs

⚠️ MythicArmor 3D models are incompatible with external entity shaders, such as plugins/ModelEngine/config.yml's create-shader option. You can safely set this to false on modern versions to ensure compatibility.

MythicMobs

Obviously as a Mythic plugin, you can load armor .bbmodel files from Mythic Packs from the <pack>/armors/ directory.

MythicCrucible can handle merging MythicArmor's Resource Pack automatically if configured in the plugins/MythicArmors/config.yml or the plugins/MythicMobs/config/config-generation.yml file as an import directory.

Nexo

MythicArmors can also hook its resources into Nexo's Resource Pack generation if configured in the plugins/MythicArmors/config.yml file.

Vendor Best Practices

Configurations

Do not include/override plugin configuration values in pack distributions. Instead, instruct in a README, installation-instructions, or in support tickets what values to change in files as needed. (For example, the plugins/ModelEngine/config.yml create-shader value can cause conflicts, and should be instructed to the user to modify, not be modified in pack file distribution)

Model UV texture naming/namespaces

The texture names and directories in .bbmodel files can carry over into pack generation and cause conflict issues. Naming Blockbench textures things like texture can result in generic texture.png files overwriting one another and causing issues. Instead, keep file names specific, such as super_armor_textures1 so the resulting file is unlikely to have conflicts.

Additionally, manage the file's namespace to match the pack to ensure minimal conflicts with other files. This setting is typically available, and defaults to blank, in .bbmodel Texture properties.