The same file
Most add-ons coexist because they add files with unique names. A conflict happens when two packs replace the same vanilla path, such as entities/player.json, entity/player.entity.json, a texture, a client entity, or a UI file.
Files with the same filename do not conflict by name alone. The full path and the pack type matter. Two files called config.json in unrelated folders can work normally.
Pack priority
Within a pack type, Minecraft uses the copy from the higher-priority pack when two active packs provide the same path. In a world's pack list, the pack shown higher in the list normally has priority over the pack below it.
- Behavior Pack conflicts are resolved in the Behavior Pack list.
- Resource Pack conflicts are resolved in the Resource Pack list.
- Moving a pack higher can make one feature appear, but it can also hide another feature that used the same file.
- Dependencies and pack stacking can affect the final order, so verify the active order in the world's settings.
Priority is a choice between complete file versions, not a merge. If both files contain useful changes, create one combined file instead.
Common conflicts
- Player behavior: two packs provide
player.json. - Player visuals: two packs provide
player.entity.json. - UI: two packs replace the same screen or UI definition.
- Textures and models: a pack replaces a vanilla asset that another pack also edits.
- Commands and scripts: both packs use the same function names, scoreboard objectives, or script identifiers.
Troubleshooting
- Make a world backup and record the active Behavior Pack and Resource Pack order.
- Disable packs in small groups until the feature starts working again.
- Check the suspected packs for the same path, identifier, event, objective, or UI screen.
- Try changing priority to confirm that the problem is an overwrite rather than a missing dependency.
- Merge the files that must both be active, then validate and test the merged version.
Use the JSON file merger for JSON-based conflicts. For the two player files specifically, read player.json and player.entity.json.