Designing GUIs for Nexo

Nexo builds the resource pack itself. What it needs from you is a glyph definition per image, the textures, and the text in its own notation - and that is exactly what this editor hands over.

What the export contains

The Output panel has a Nexo tab with three things: the title or text for the open module, ready to paste; the glyph configuration for the whole project; and the folder as a ZIP, with config, textures and fonts in the structure Nexo expects. Unpack it into your server's plugins/ folder.

The positions stay exact

The plugin output is read from the same layout as the preview. Nexo assigns its own characters, but a glyph's position only depends on its texture, height and ascent - so it lands on the same pixel either way. Offsets become Nexo's shift tags.

Glyph names you can read

Glyph ids are built from the module and element name: module *Shop* with element *Background* becomes shop_background. Rename elements in the editor and the config follows. The text and the configuration belong together - when one changes, take both.

What Nexo will reject

Two things, and the editor lists both as warnings before you upload anything:

• textures larger than 256 × 256 pixels
• an ascent above the height - an image placed higher than its box allows

What carries over

Colours, shadows, moved or resized text and bold or italic runs all survive the trip to Nexo. The editor's own resource pack export is the alternative if you would rather not run a glyph plugin at all.