Cosmetics and furniture: choose the plugin role before the pack

A model is not the whole integration

A furniture model needs a definition that tells the server how it is placed and interacted with. A wearable cosmetic also needs a system that equips and manages it. These are different jobs, even when the artwork comes from the same collection.

Nexo, ItemsAdder and Oraxen each document furniture functionality. HMCCosmetics documents item integrations for all three. That is evidence of integration routes, not evidence that every pack works on every server stack.

Choose one supported item configuration

Start with the configuration actually supplied by the pack author and the plugin already responsible for your server's custom items. The presence of three integration options is not an instruction to install all three together. If changing plugins, treat configuration migration as separate work rather than assuming matching model files make the definitions interchangeable.

Compare the behavior you need

For furniture, ask about placement surfaces, rotation, collision and interaction. For cosmetics, ask about supported equipment slots and the cosmetics plugin expected by the pack. A screenshot can show the artwork but cannot answer those behavior questions.

• Identify the supplied plugin configuration and any separately required plugins or licenses.
• Check the pack's documented constraints rather than inferring support from a plugin name.
• Test the selected pack and exact versions in a staging server before rollout.

Where instructions belong

Use Erocavontic's installation Docs for the pack-installation workflow and the plugin owner's documentation for plugin-specific mechanics. These articles explain roles and review questions; they are not tested installation guides or a certification of Store products.