Find duplicate Oraxen item IDs before merging a pack

Two content packs can define the same internal item ID. Compare their definitions before merging files so one pack does not silently change an item players already own.
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
Export the current item definitions and list their internal IDs. Compare the incoming pack in a separate directory, including recipes and mechanics that reference those IDs.
Mark duplicate IDs and decide which existing identity must remain stable. A new filename or display name does not necessarily create a new item identity.
Import a small nonconflicting section into staging and inspect startup warnings. For each collision, plan a new unique incoming ID and update its references consistently before loading it.
Test representative existing items alongside fresh incoming items. Check recipes and interactions, not just their models, because two items can look different while sharing conflicting definitions.
Verify the result
Every intended item should resolve to a single definition, and the incoming content should not change the behaviour of existing owned items. Referencing recipes should produce the correct unique output.
If the result differs
If the wrong item appears, search all loaded definition files for its ID. If only its texture is wrong, inspect model references after resolving ID collisions rather than renaming more live items.
Keep a recovery path
Restore the complete previous definitions and generated pack if the merge changes existing content. Do not remove player inventory data to resolve a collision; keep the incoming pack isolated until its IDs are consistent.
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.