Separate an Oraxen missing glyph from a missing permission

Applies to: Oraxen; match the linked maintainer documentation to your installed platform and release.
Documentation checked 9 November 2026.

A player seeing raw glyph text may have a pack, permission or formatting problem. Compare the same glyph in two accounts before editing the image or granting broad access.

Check the installed content

Oraxen combines server-side item definitions with client resource-pack assets. Check the installed release before copying a recipe or component example, because Minecraft item formats have changed between releases. Work on a staging copy for changes that affect existing player items.

Work through the change

1. Record the exact glyph identifier and the text players type or the menu sends. Verify the installed-release syntax rather than assuming another plugin uses the same placeholder.
2. Test the glyph on staging with one administrator and one ordinary account using the same accepted pack. Compare chat output with a server-generated message containing the glyph.
3. Inspect the permission rules documented for that glyph and its integration. Grant only the intended narrow permission to a temporary test group and repeat the ordinary-player test.
4. Revoke the temporary grant and test the denied case again. If permissions work, compare the client pack version and the formatting path used by the failing message.

Verify the result

The authorised player should see the intended glyph in supported contexts, and the denied case should follow the documented restriction. Neither account should need operator status for routine glyph use.

If the result differs

If both accounts fail, inspect pack generation and the glyph character mapping. If only one chat format fails, trace its escaping or placeholder processing before changing the glyph file.

Keep a recovery path

Remove the temporary permission group and restore the previous glyph configuration if necessary. Keep a record of the exact node tested so production access can be granted deliberately without using wildcard permissions.

References and related help

Check the maintainer reference: Oraxen documentation.

Before changing live data, read how to keep a completed recovery copy. For startup errors, use the log collection guide.