1.0.6
Compatibility
Changes
Glypher
Glypher is a client-only Fabric mod for aligning custom title glyphs inside vanilla Minecraft GUI screens.
Authors: LmVictor20 x ChatGPT
What Glypher does
Glypher helps you build GUI title layouts directly in-game:
- choose a vanilla menu type;
- enter the glyph character used as the title;
- preview the real vanilla screen;
- move the title horizontally with offset glyphs;
- move the title vertically with a virtual ascent preview;
- save the final result into an export file for your resource pack.
After saving, Glypher creates a text export file with:
IDTitleAscent
Supported version
- Minecraft
1.21.3 - Fabric Loader
- Fabric API
Installation
- Put the Glypher mod jar into your
modsfolder. - Prepare and enable a resource pack with your custom GUI glyphs.
- Make sure your resource pack contains
assets/minecraft/font/default.json. - Start the game.
- Use
/glypher create.
Where to place default.json
The file must be placed inside your resource pack here:
<YourResourcePack>/assets/minecraft/font/default.json
If default.json already exists, do not blindly replace it.
Merge the providers from your current file with the Glypher example.
Included example
This repository includes an example file here:
resourcepack-example/assets/minecraft/font/default.json
You can use it as a base template for your own pack.
How to prepare the resource pack
Minimal structure:
MyPack/
pack.mcmeta
assets/
minecraft/
font/
default.json
mynamespace/
textures/
gui/
my_menu_title.png
my_small_menu_title.png
my_beacon_title.png
Important notes:
- custom title images are usually added with a
"type": "bitmap"provider; - horizontal movement is done with a
"type": "space"provider; - the
Ascentexported by Glypher should be copied into the"ascent"value of the matching bitmap provider; - if you already have a working
default.json, you usually only need to add the missing bitmap providers and the offset glyphspaceprovider.
Example default.json
The included example contains:
- several bitmap providers for GUI title images;
- one
spaceprovider with offset glyphs used by Glypher.
The space block uses the same offset glyphs expected by the mod:
\uF800to\uF80Afor positive horizontal movement;\uF80Bto\uF815for negative horizontal movement.
Example:
{
"type": "bitmap",
"file": "mynamespace:gui/my_menu_title.png",
"ascent": 24,
"height": 256,
"chars": [
"\uE120"
]
}
How Glypher works step by step
- Run
/glypher create. - Select the vanilla menu type you want to edit.
- Enter the glyph character used as the menu title.
- Open the preview screen.
- Adjust the title on the
Xaxis. - Adjust the title on the
Yaxis. - Visually align the title until it looks correct.
- Press
Save. - Enter a layout ID.
- Open the generated export file.
- Copy the exported
TitleandAscentinto your resource pack setup.
Commands
/glypher create- create a new layout/glypher list- open the saved layouts screen
Saved data
Glypher stores:
- layout data in
config/glypher/layouts.json - exported text files in
config/glypher/exports/
Understanding X offset
Glypher does not move the title by raw screen coordinates. Instead, it builds the final title text like this:
<offset glyphs> + <your title glyph>
That means special shift glyphs are inserted before the main glyph to move the title left or right.
Understanding Y offset
Glypher previews vertical movement in-game as a virtual offset.
When you save the layout, Glypher gives you a recommended Ascent value.
That value should be placed into the bitmap provider for the glyph in default.json.
Example:
{
"type": "bitmap",
"file": "mynamespace:gui/my_menu_title.png",
"ascent": 24,
"height": 256,
"chars": ["\uE120"]
}
Typical workflow
- Draw your GUI title image.
- Bind it to a glyph in
default.json. - Start the game with the resource pack enabled.
- Run
/glypher create. - Choose a menu type.
- Enter the title glyph.
- Align the title in the preview.
- Save the layout.
- Copy the exported values into your final resource pack configuration.
Screenshot placeholders
Menu Selection

Glyph Input

Preview Screen

Saved Layouts

Credits
LmVictor20 x ChatGPT
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:OSabMJje:zhmXFJU9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:OSabMJje:zhmXFJU9"
}

