Check an Oraxen item component against the Minecraft version

A custom item can lose a behaviour after a Minecraft update even when its model remains correct. Check the supported component format before replacing player items or changing the texture.
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 exact Minecraft, Paper and Oraxen versions and the affected item ID. Keep a copy of its current definition and one representative existing test item.
Open the item documentation for that release and identify the behaviour field involved. Do not mix a legacy item setting with a newer Minecraft component example unless the release supports it.
Create a new staging item ID with only the base material and affected behaviour. Obtain a fresh copy and test the relevant interaction without optional mechanics.
Compare the fresh simplified item, the full new item and the existing old copy. This separates an unsupported definition from item-update behaviour or another mechanic.
Verify the result
The fresh item should have the intended behaviour on the supported server version. Existing copies should change only according to the item-update policy documented for your installed build.
If the result differs
If the simplified item fails, inspect loading warnings and version support. If only old copies differ, investigate the supported updater path; a resource-pack rebuild alone does not rewrite stored server-side item data.
Keep a recovery path
Restore the earlier definition and keep valuable player items untouched while testing. If an item migration is necessary, prepare a separate backed-up procedure rather than distributing replacements during diagnosis.
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.