Troubleshooting & FAQ
Troubleshooting
| Symptom | Fix |
|---|---|
| Player gets kicked: "Cannot interact with self!" when clicking | Your PacketEvents is older than your Minecraft version. Update PacketEvents (its dev builds if needed). Clicks are self-interact packets; an outdated mapping lets one leak through unhandled |
| Menu shows squares / missing art | The resource pack isn't applied — re-run /nxgui confirm within 30 s of applyedit, or check your server pack URL + hash are current |
Placeholders show literally (%player_level%) | PlaceholderAPI (and the relevant expansion via /papi ecloud) isn't installed |
| Custom font renders a different size in game | Nudge that font's Font size in the text inspector — fonts carry their own metrics |
| Anvil input art misaligned | /nxgui skinalign <x> [y] live, then persist the values under skin: in config |
| Menu won't open mid-air / on a horse | By design (stability.close-on-fall, vehicle guard) — land or dismount first |
| Clicks land slightly off | /nxgui hitdebug visualizes hitboxes; calibrate under cursor: if your setup needs it |
| Deploy link dead / session expired | Links are one-time and sessions idle out — just run /nxgui editor again; your project round-trips from the server |
FAQ
Will it lag my server? No. Rendering is fully client-side — the server only tracks hitboxes and runs your logic. Load-tested with 100 concurrent players viewing GUIs: 0% TPS drop (verified with an independent profiling tool).
Folia? Yes — native support (folia-supported: true), every operation region-safe.
Can other players see my menu? No. Everything is per-viewer packets; two players can use the same screen independently at once.
Do I need to edit JSON? Never. The editor round-trips your whole workspace; treat screens/ as build output.
Multiple GUIs? One project holds unlimited screens — all deployed together, each with its own command/permission.