All versions
1.0.4
Release
glowworks-1.20-1.0.4-forge.jar2 weeks ago 25
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Required content
Changes
v1.0.4
CHANGES:
- All of blocks with
minecraftas mod_id will be excluded in emitter.toml & filter.toml- REASON: Colorful Lighting Sodium Compat now included these blocks with
minecraft
- REASON: Colorful Lighting Sodium Compat now included these blocks with
- Tweaked the
emitter.tomlfor:- glowstones to be "yellow", 255,255,0 (rgb)
- dark_red to be 127,0,0 (rgb)
- dark_green to be 0,127,0 (rgb)
- dark_blue to be 0,0,127 (rgb)
v1.0.3
UPDATED:
glowworks-client.toml: save_debug_resources is now defaulted to "true" and it will be saved in~/.minecraft/debug/...
v1.0.2
UPDATED:
- Fixed "crash" related to the missing license in mod 🤦🏻♀️... now everything is working properly.
v1.0.1
UPDATED:
- Corrected the required version for Colorful-Lighting in mods.toml
v1.0.0
Colorful-Lighting (Glowworks) - Initial v1.0.0
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:ovkxGO8r:TSU0kTzE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ovkxGO8r:TSU0kTzE"
}


