Furniture interaction, states and hitboxes
Furniture can be static, sit-able or interactive. The source sample documents multiple hitboxes, multiple seats and an optional state engine.
Think in three layers
- Visual:
modelanddisplaycontrol appearance and position. - Interaction area:
hitboxesdefine where players can interact. - Behavior: optional
statescan change the model, hitboxes, seats and sounds.
For example, a door or chest can use a default closed state and open state. states.toggle-on-interact: true allows interactions to switch state. Within a state, hitboxes: [] explicitly disables the hitboxes for that state.
Rotations
placement.rotation.mode: SNAP with step: 45 is a documented way to snap placement rotation. For fine positioning, the sample exposes display.offset.x/y/z, display.scale and optional per-state display.yaw-offset.
Debugging order: verify model origin, placement rotation, display transform, then hitbox/seat offsets. One axis at a time is easier to debug than changing the whole model.
Build and edit without guesswork
Build two visible states named closed and open; test interaction and adjust hitboxes for each state. Rotating the visual does not automatically relocate a badly configured hitbox.
Verification: save the YAML, run /obsidrel reload, inspect errors and test one feature at a time. For model or texture changes, rebuild and send the pack.
See every field documented in the shipped example in YAML field reference.