Diagnose an Oraxen cooking recipe with the wrong timing
Applies to: Oraxen; match the linked maintainer documentation to your installed platform and release.
Documentation checked .
Cooking recipes have processing settings beyond their input and output. Compare one furnace process at a time before changing every custom recipe or the server tick rate.
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
- Record the cooking type, expected input, output, processing duration and experience. Check the current Oraxen recipe reference for the units and fields supported by your release.
- Copy the recipe to a unique staging name. Set an observable processing duration and a low-value result so a mistake cannot create valuable items.
- Load the test recipe through the release-supported workflow and use the matching cooking block. A furnace, smoker and blast furnace do not accept all the same recipe types.
- Time several individual operations while the server runs normally. Check the consumed ingredients and experience separately, then repeat with a vanilla control recipe in another block.
Verify the result
The custom process should use the intended block and timing without changing the vanilla control. Record server tick performance if wall-clock duration differs from the configured processing time.
If the result differs
If the recipe never starts, inspect its type and ingredient matching before shortening the duration. If every recipe runs slowly, investigate server tick delay rather than multiplying the custom cooking speed.
Keep a recovery path
Restore the earlier custom recipe and remove only the disposable furnace contents. Preserve the world save before testing automation around custom cooking, because a recipe rollback cannot retrieve already processed materials.
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