Commands

Inspecting

/holopanels list

Every board and whether it is placed.holopanels.admin (root command)

/holopanels info <board>

Show the compiled root view, anchor, distances and visibility condition.holopanels.admin (root command)

/holopanels debug

What is currently rendered to you, including which view your session is on. The first thing to run when a panel is not where you expect.holopanels.admin.debug

/holopanels validate

Parse the whole configuration and report problems without applying anything. Safe to run on a live server.holopanels.admin.reload

Applying changes

/holopanels reload

Re-read boards and views. Builds everything first and swaps it in only if it parsed; a bad edit leaves the running configuration alone.holopanels.admin.reload

/holopanels refresh [board]

Redraw without re-reading files. Drops cached provider content, so a provider is asked again.holopanels.admin.debug

Placing

/holopanels here <board>

Put the board at your feet, facing the way you are looking.holopanels.admin.move

/holopanels wall <board> [gap]

Raycast up to 12 blocks, sit the board just off the face it hit and work out the yaw so it faces out of the wall. Usually what you want.holopanels.admin.move

/holopanels move <board> <x> <y> <z> [yaw]

Exact coordinates. ~ keeps the current value for that coordinate.holopanels.admin.move

/holopanels nudge <board> <direction> [distance]

Shift along the board's own axes: right, left, up, down, forward, back.holopanels.admin.move

/holopanels unplace <board>

Drop the anchor and keep the board defined, ready to place again.holopanels.admin.move

/holopanels remove <board> confirm

Delete it from boards.yml, taking its view binding, distances and conditions with it.holopanels.admin.remove

Permission reference

Node	Default	Controls
`holopanels.use`	everyone	Clicking and interacting with visible boards
`holopanels.admin`	operator	The root administrative command
`holopanels.admin.reload`	operator	`reload` and `validate`
`holopanels.admin.move`	operator	`here`, `wall`, `move`, `nudge`, `unplace`
`holopanels.admin.remove`	operator	`remove` / `delete`
`holopanels.admin.debug`	operator	`debug` and `refresh`

list and info have no subcommand-specific check, but the root /holopanels command requires holopanels.admin as declared in plugin.yml.

Reporting a problem

Include the output of /holopanels debug and /holopanels validate. Between them they cover which view your session was on, what the renderer thought it was drawing, and whether the configuration parses at all, which is most of what anyone would ask you next.

Arguments in <angle brackets> are required; [square brackets] are optional. The /hpanels alias accepts the same subcommands and permissions.