Tags
Creators
Details
Licensed MIT
Published 6 months ago
Updated last week
All versions
1.8.0-NeoForge-1.21.1
Release
Glint & Glamour v1.8.0 Forge [1.21.1]last week 160
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
[1.8.0]
Added:
- Glint rules: give an item a permanent glint you designed, no code needed. Put the glint on an item, hold it, and run /glint rule loot <loot table> (glinted whenever that table drops it, like a boss drop or a chest), /glint rule drop <mob> (glinted whenever that mob drops it), or /glint rule item (every copy of the item shows it, wherever it came from). /glint rule list shows them, /glint rule remove <item> deletes an item's rules (add loot, drop or item to remove just that kind), and /glint rule reload picks up hand edits to the file
- Rules save to config/glint-and-glamour/rules.json, so a modpack can set them up in a test world and ship the file
- For mod developers: CustomGlint.registerItemGlint gives every stack of an item a glint at render time, smithed and /give'd copies included. Render code reads it through CustomGlint.readForRender
Altered:
- A 1.8.0 server and client must match. An older client joining is turned away at login with a version message
Fixed:
- Printing at the Glint Table now grants the trim advancements, unlocks a matching imported trim, and adds the trim to your printed library. Before, this only worked when your inventory was full
- /glint extract keeps a single-layer glint's simultaneous setting and chromatic pattern
- The server now clamps the opacity a Glint Table print asks for, so an out-of-range value can no longer skip the glass cost
- An enchanted item with a custom glint no longer shows the vanilla enchantment shimmer underneath it. Armor, elytra, compasses, shield banners and modded armor all hid it only partly, or not at all
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:KeOUoe88"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EPurgfyc:KeOUoe88"
}

