Build an Oraxen recipe without replacing another recipe
Applies to: Oraxen; match the linked maintainer documentation to your installed platform and release.
Documentation checked .
A custom recipe needs its own identity as well as the correct output. Use a disposable recipe to check ingredients, quantities and discovery before changing a recipe players already use.
Check the installed content
Oraxen combines server-side item definitions with client resource-pack assets. Check the installed release before copying a recipe or component example, because Minecraft item formats have changed between releases. Work on a staging copy for changes that affect existing player items.
Work through the change
- Inventory the existing recipe files and record the intended output item ID, amount and recipe type. Keep a backup of the recipe folder before opening the builder.
- In game on staging, open the required player-only builder, such as
/oraxen recipes builder shapedfor a shaped recipe. Fill its inputs and output, then save a new descriptive name with/oraxen recipes save <name>. - Inspect the saved definition and confirm that its name does not overwrite another recipe. Test the exact ingredient arrangement and one arrangement that should fail.
- Test with an ordinary player who has the intended recipe permission. Repeat with insufficient ingredients and with a full inventory, observing where the crafted result goes.
Verify the result
The output should have the correct Oraxen identity and amount, and each craft should consume the intended ingredients. An unrelated recipe should still produce its original result.
If the result differs
If an administrator can craft but a player cannot, check recipe permissions and discovery. If the wrong item appears, inspect the output ID before rebuilding textures; recipe logic and client appearance are separate.
Keep a recovery path
Restore the previous recipe directory and restart the staging server if the new recipe overrides an existing one. Keep the failed recipe outside the loaded folder while comparing names and ingredients.
References and related help
Check the maintainer reference: Oraxen documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.
No comments to display
No comments to display