Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated last week
All versions
1.2.0
Release
Custom Glints 1.2.06 months ago 56
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
[1.2.0]
Added:
- JEI integration: all Glint Trim, Tear, and smithing recipes now display in JEI.
- 35 new glint designs (55 total, up from 22). New: arcs, aurora, blobs, cascade, chevron, coral, cracks, debris, dunes, feather, frost, glitch, glow, halo, lightning, marble, matrix, mesh, mosaic, net, oil, petal, plasma, plate, prism, sand, sheen, shimmer, silk, slash, smoke, static, tide, tile, weave.
- Blank Glint Trim duplication: trims with no colors can now be duplicated with the same 3x3 diamond recipe (Trim + 7 Diamonds + Glowstone Dust → 2 copies). Previously only trims with at least one color could be duplicated.
- Trim speed recipe: combine a Glint Trim with 1–8 Redstone Dust to set its animation speed (1 = 1x, 8 = 8x). Craft again with a different count to change it.
- Trim scale recipe: combine a Glint Trim with 1–8 Slimeballs to set the pattern zoom (1 ball = 0.5x zoom in, 8 balls = 4.0x zoom out). Craft again to change it. Scale carries through to the item when smithing.
- Data-pack design support: mods and data packs can register custom designs via data/<namespace>/customglint/designs/*.json. Registered designs appear in the editor picker, command suggestions, and the creative tab.
- The Glint Editor design picker is now a searchable scrollable overlay showing all 55 built-in designs plus any data-pack designs, replacing the old fixed grid of 22 buttons.
- /glint apply now accepts two additional optional arguments: scale (0.25–4.0) and simultaneous (true/false). Tab completion now covers all 55 designs.
Removed:
- dots and skulls designs.
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:EPurgfyc:4ZZMC8hI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EPurgfyc:4ZZMC8hI"
}

