Check a Nexo furniture hitbox independently of its model
Applies to: Nexo; match the linked maintainer documentation to your installed platform and release.
Documentation checked .
A furniture model can look correct while blocking the wrong space or accepting clicks in an unexpected area. Use an empty test plot to compare appearance and interaction boundaries.
Check the installed content
Nexo manages custom content through item definitions, resource-pack files and optional mechanics. A correct item identifier does not prove that the client received the matching pack. Follow the documentation for your installed build and keep its generated assets with the source definitions.
Work through the change
- Record the furniture ID and the intended placement and collision area. Follow the hitbox documentation linked from the mechanic index for the installed release and supported entity type.
- Back up the test world and furniture definition. Place a single expendable copy on a clear floor without region protection or nearby decorative entities obscuring the result.
- Approach from every side and test movement, targeting and the intended interaction. Compare the visible edges with the area that actually blocks or accepts the player action.
- Change only the selected hitbox property on staging and retest a freshly placed copy. Include removal and replacement so an old placed instance does not hide the effect of the definition change.
Verify the result
The furniture should occupy the intended space and remain usable and removable through its documented interaction. The test should leave no unexpected invisible obstacle after normal removal.
If the result differs
If the visual model is wrong, troubleshoot pack delivery separately. If only protected plots differ, inspect the protection integration before enlarging a hitbox or granting players bypass permissions.
Keep a recovery path
Restore the previous definition and the small staging-world checkpoint if the trial leaves inconsistent placed objects. Avoid editing live decorative areas or deleting nearby entity types as a shortcut to removing one test object.
References and related help
Check the maintainer reference: Nexo documentation.
Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.
No comments to display
No comments to display