Oraxen furniture: model paths, collision and cosmetic handoffs

The model and the mechanic are different pieces

Oraxen's Creating furniture tutorial describes furniture as an Oraxen item with the furniture mechanic. Its example references a model in the resource pack and then defines display-entity furniture behavior. This separation is useful when diagnosing whether a problem belongs to an asset reference or to placement mechanics.

The tutorial describes Pack.model as a path below the pack's models directory without the .json suffix. When reviewing a supplied pack, check that the definition and exported model agree; do not infer correctness from a familiar item name.

Correct the model before compensating in placement

The Oraxen tutorial advises fixing base orientation in Blockbench and using scale and translation for small placement adjustments. It also distinguishes a simple hitbox from multiple collision areas. Those distinctions provide review questions for irregular objects rather than a universal configuration recipe.

• Confirm the exported model's base orientation with the author.
• Review whether the intended collision is simple or needs multiple areas.
• Observe texture, collision and rotation separately in staging; a successful load is not the whole acceptance test.

An Oraxen item is not automatically a cosmetic

HMCCosmetics documents the material reference oraxen:<itemid> for its Oraxen item integration. This is a handoff to the cosmetics system, separate from the furniture mechanic. A placeable decoration does not become an approved wearable merely because it has an Oraxen item ID.

For a cosmetics purchase, confirm that the author supplies the intended equipment configuration and documents its requirements. For furniture, review the placement definition. No exact versions or retained Erocavontic products are certified by this explainer.