CMD Prefixing#

Summary

Formatting your custom_model_data to avoid clashing with other packs

Required

Any usage of the custom_model_data field on custom items based on vanilla item models

Example

Items from Gamemode4 should have custom_model_data that use strings with a gm4 namespace

Important

The convention is largely unneccessary with modern Minecraft changes. Since the introduction of item components in 1.20.5, the new item_model component can be used to display any item model on any item which allows for extremely flexible displaying of custom items.

The only use-case for this convention for now is to still support packs who rely on overriding vanilla item files in order to display optional textures for custom items.

The custom_model_data component defines several types of data that can help you avoid conflicts with other packs' custom items. This is only neccessary in the context where a creator wants to create a data pack with an optional resource pack. Since there are not many packs with these requirements, it's likely any risk of conflict is minimal.

The best case is to use the strings subcomponent field of the main component and define values that are using your namespace as a prefix. This ensures proper compatibility for people overriding the same vanilla files (relying on weld to merge said files). You could also use the other fields such as flags and such with namespacing.

Example

I have a cool sword texture I want to apply to the diamond sword model, instead of using CustomModelData 1, I would use CustomModelData 4250001