1.0.0
Compatibility
Changes
Glazed
Glazed re-skins DonutSMP’s reworked server menus into the tidy double-chest GUIs you already know — with real item icons, player heads, and proper tooltips.
Client-side only: every click still talks to the server exactly as before. Nothing about gameplay changes — it just looks right again.
Features
Main Menu
- Clean 5×2 chest-style icon grid
- Replaces the long button list
- Open with
G
Friends
- Real player heads with skins
- Oak-sign search UI
- Clean glass-pane accept/decline buttons
Orders
Choose Item
-
Paginated chest GUI
-
True item icons
-
Correctly tinted:
- Potions
- Tipped arrows
- Bottles
Search
- Familiar sign editor input
Create Order
-
Item, quantity, and price on one screen
-
Single confirm button
-
Supports:
KMBamount formats
-
Minimum price enforced automatically
Enchantments
- Selected using enchanted books
- Grouped by enchantment type
Review
- Clean order summary
- Displays item enchantments properly
Homes
-
Beds for set homes
-
Your chosen home icons displayed correctly
-
Black glass for empty slots
-
Red glass for locked slots
-
Tidy manage screen with:
- Teleport
- Rename
- Delete
-
Home renaming uses a sign editor
Settings
- Every option on a single screen
- Thematic icons
- Clear ON/OFF states
Stats & Leaderboards
- Baltop-style player heads
- Relevant stat/value shown directly
Compatibility
- Minecraft:
1.21.6 - 1.21.11 - Mod Loader: Fabric
- Requires: Fabric API
Installation
- Install Fabric Loader
- Install Fabric API
- Drop Glazed into your
modsfolder
That’s it — the re-skins apply automatically whenever a supported menu opens.
No setup. No config. No server install required.
Disclaimer
Glazed is an unofficial, fan-made mod. It is not affiliated with, endorsed by, or associated with DonutSMP.
This mod only changes how menus look on your own client.
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:ipik5SPK:86go1Wyt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ipik5SPK:86go1Wyt"
}

