Nexo furniture and cosmetics: separate model presentation from equipment

Furniture has its own display context

Nexo's Furniture Mechanic documentation describes display_transform as the context used to display a model. It also documents translation, scale and rotation properties. These controls explain why a model's appearance in a placed object can differ from an equipment view without the texture itself being wrong.

Review the intended display context with the pack author before treating a misplaced or incorrectly sized object as a broken asset. Visual adjustments and the furniture's hitbox are separate concerns; looking correct does not demonstrate correct collision.

Placement rules are part of the design

Nexo documents limited placement on floors, walls and roofs, as well as rotation restrictions. These are choices in a furniture definition, not features automatically promised by every furniture pack. A decorative wall piece and a floor table can need different placement rules even within one collection.

• Confirm the intended surfaces and orientations for each selected object.
• Review the configured hitbox independently of visual scale.
• Record any expected interaction, sound or drop behavior before staging tests.

Cosmetics use a separate item handoff

HMCCosmetics lists the Nexo item integration using the material form nexo:<itemid>. That reference identifies an item; it does not by itself define which cosmetic slots a pack supports or prove how the asset behaves when equipped.

For a cosmetics pack, request its HMCCosmetics configuration and supported-slot notes alongside the Nexo item definition. For a furniture pack, focus instead on placement and interaction. Neither workflow can be certified from the existence of the integration alone.