Owned Objects
Definition
Some in-world objects (items, entities) can be marked as owned. Owned objects SHOULD NOT be treated like default/regular Minecraft objects, but MAY still be accessed by any datapack.
Generally, owned indicates a "custom" object.
The following are definitions of owned objects:
Items
Items with -:true in their minecraft:custom_data component.
Entities
Entities with the '-' entity tag, excluding players.
Handling Owned Objects
As stated in the definition, owned objects SHOULD NOT be treated as default/regular Minecraft objects, but SHOULD still be recognized as objects of their type.
Examples:
- A datapack that converts
stone_pickaxes tocopper_pickaxes SHOULD NOT convert ownedstone_pickaxes. - A datapack that adds item transport pipes SHOULD transport owned items the same as regular items.
- A datapack that increases the health of zombies SHOULD NOT increase the health of owned zombies.
- A datapack that adds a weapon that knocks back mobs SHOULD knock back owned mobs.
It is important to note the difference between private and owned: private objects MUST NOT be interacted with at all (other than by the defining pack); owned objects MAY be interacted with, but should not be treated as standard objects.