Erocavontic journal

ItemsAdder furniture entities and namespaced cosmetics

Why furniture entity choice and namespaced item references answer different integration questions.

By Erocavontic Creation. Published , updated

Entity choice affects the review

ItemsAdder's furniture documentation distinguishes item_display, armor_stand and item_frame furniture. It describes display transformations for item_display and surface-oriented placement for item_frame. Read the definition supplied with a pack before assuming that two visually similar pieces use the same behavior.

The documentation also distinguishes visual transformations from hitbox configuration. A model that looks correctly positioned can still need a collision review. Use the author's configuration and documentation for your installed version rather than copying a different furniture entity's settings.

Check geometry, not just the thumbnail

The ItemsAdder documentation discusses hitbox dimensions and offsets, including a width/length restriction for item_frame furniture. These details matter when reviewing wide tables, wall decorations or objects that should remain passable. They should not be generalized into a promise about an untested pack.

  • Identify the furniture entity in the supplied configuration.
  • Write down intended wall, ceiling or floor placement.
  • Check model position and hitbox alignment separately on the target stack.

Cosmetic references include a namespace

HMCCosmetics documents ItemsAdder material references in the form itemsadder:<namespace>:<item>. Keep the namespace with the item identifier when reviewing the handoff between configurations; a display name is not a substitute for that reference.

This integration connects the item definition to the cosmetics system. It does not show which slots, animations or pack-specific features are supported. Ask for the supplied cosmetics configuration and constraints before choosing the pack. Installation steps remain in the canonical Docs.

Sources and installation documentation

Independent editorial context, not official plugin documentation or a tested pack compatibility claim.

Read the installation Docs