On this page

In-Game: Runtime, Commands & Permissions

What opening a menu does

  • The player's camera locks facing the menu; their mouse moves a real cursor across it. Only they can see it.
  • Hotbar/hand are visually masked for immersion; everything is restored perfectly on close.
  • Left and right click are separate inputs. Sliders drag with hold-right-click. Sneak is swallowed (never closes or dismounts).
  • Menus refuse to open mid-air (unless flying) or while riding a vehicle — configurable safety.

What closes a menu

CauseNotes
Close button / logicElement behavior or the Close Menu node — your job to include one!
/nxgui stop [player]Admin escape hatch
Taking damagestability.close-on-damage (default on) — the damage still applies, the GUI just frees them to react
Falling / external teleport / world change / quitAutomatic cleanup, control always returns cleanly

Commands

CommandWhat it does
/nxgui run <screen> [player]Open a screen — for yourself, or for a target (console-friendly: wire it into joins, NPCs, other plugins)
/nxgui stop [player]Force-close
/nxgui reloadReload config + screens; viewers get closed & reopened onto the fresh version
/nxgui editorMint a one-time web-editor link with your workspace
/nxgui applyedit <uuid>Pull a deployment: screens + project + pack, hot-applied
/nxgui confirmAccept the queued resource pack (30 s window after applyedit)
/nxgui testinput · skinalign <x> [y] · hitdebugDebug helpers: preview the input UI · nudge the anvil skin alignment live · visualize hitboxes

Alias: /nxg. Plus every screen's own open command registered from the editor.

Permissions

PermissionGrantsDefault
nxgui.start/nxgui runOP
nxgui.stop/nxgui stopOP
nxgui.reloadreload · editor · applyedit · confirmOP
per-screen permissionSet in the editor; checked on every open pathpublic if empty

Normal players don't need any nxgui.* permission — they open menus through screen open-commands, NPCs or your plugins.

Last updated July 11, 2026