Currently in Bedrock Edition, when two crafting recipes share the exact same pattern and ingredients, the crafting system cannot handle the conflict properly. One recipe permanently overrides the other, making certain items completely uncraftable.
Unlike Java Edition, which provides tools to manage recipe priorities and data pack overrides, Bedrock Edition lacks a native framework to resolve recipe collisions. This causes major issues when playing with multiple Add-Ons, Marketplace content, or custom JSON recipes.
### The Problem
* **Recipe Overriding:** Duplicate patterns lock players out of crafting specific items.
* **Add-On Conflicts:** Creators cannot specify how custom recipes interact with vanilla or third-party content.
### Proposed Solutions
1. **Recipe Output Cycling (UI Feature):** If a pattern matches multiple valid recipes, allow players to click or select the output slot to cycle through all available crafting results.
2. **Recipe Priority in JSON (Creator Feature):** Add a priority attribute to Bedrock’s recipe JSON files, allowing creators to define recipe precedence and prevent Add-Ons from breaking vanilla or modded content.
Fixing recipe conflict resolution would greatly improve Quality of Life for casual players and give Add-On creators the stability needed to build complex experiences.
0 Comments
Please sign in to leave a comment.
Post a new comment: