player.json and player.entity.json

Two files that commonly need special care

player.json

player.json is a Behavior Pack file that changes the player entity. Add-ons use it for player components, component groups, events, and other behavior that cannot be added by a separate custom entity.

Because it describes the same vanilla player as every other add-on using the file, it is a common source of compatibility problems. Keep a backup of the original file and make a copy of your world before testing changes.

Look for it in the Behavior Pack at entities/player.json. The exact location can vary between add-ons, so check the pack's manifest and folders instead of assuming every pack has the same layout.

player.entity.json

player.entity.json is a Resource Pack client-entity file. It controls client-side definitions such as player geometry, animations, animation controllers, materials, and texture assignments.

It is separate from player.json: changing behavior in the Behavior Pack does not automatically change how the player is rendered, and changing the Resource Pack file does not add behavior.

It is commonly found at entity/player.entity.json in a Resource Pack. A pack that adds custom HUD or player visuals may also reference files from this definition.

Why they conflict

These files have the same vanilla path in different packs. Minecraft does not combine two files just because both packs are active. The higher-priority pack supplies the version of that path that the game loads.

  • Two Behavior Packs can conflict through player.json.
  • Two Resource Packs can conflict through player.entity.json.
  • A Behavior Pack and a Resource Pack can both be active without conflicting with each other through these two files, because they belong to different pack types.

Merging safely

When both add-ons are needed, combine the definitions into one file rather than keeping two copies and hoping their order will work. Start with a backup, compare the files, and preserve unique keys from both packs.

  1. Copy the files into a working folder and identify which pack owns each file.
  2. Merge objects such as components, component_groups, events, animations, and controllers without duplicating keys.
  3. Update references when an animation, event, or component name is renamed.
  4. Validate the result as JSON, then test the world with only the merged pack enabled.

Open the JSON file merger to combine JSON files and inspect the result before exporting it.

For the broader rules about pack order, see Addon conflicts.