Designing GUIs for Oraxen

Oraxen wants a glyph per image and a text that uses it. The design is the part this editor does: where the image sits, how wide the title is, which offsets are needed.

From design to config

In the editor, Output → For plugins → Oraxen gives you the glyph configuration for the project, the title text for the open module, and a ZIP with the folder structure. Nothing in between needs editing by hand.

Offsets become shift tags

Where the editor places a glyph, Oraxen has to shift the text - and the shifts come out of the same layout that drew the preview. That is the whole reason the result lands on the pixel you saw.

Limits worth knowing before you build

Oraxen carries colours, shadows, moved and resized text and bold or italic runs. What it rejects is the same pair every glyph plugin rejects: a texture above 256 × 256, and an ascent larger than the height - the second one makes the client drop the entire font, so the editor blocks it rather than warn once.

If you later drop the plugin

The same design also exports as a plain resource pack with a text component, so a move away from Oraxen does not mean rebuilding the menu. The design is the source; the plugin configuration is one of several outputs.