Tags
Creators
Details
1.0.0
Compatibility
Changes
ColorApocalypse is now multi-loader: Forge, Fabric/Quilt & NeoForge
ColorApocalypse now ships on Forge, Fabric/Quilt, and NeoForge from one shared codebase, with identical features and behavior across all of them same roulette mechanic, same destruction logic, same multiplayer sync.
- Forge: 65.1.2: reworked internally to support this release. The config system was rewritten from ForgeConfigSpec to a hand-rolled JSON config (config/colorapocalypse.json), and networking, tick handling, and command registration were decoupled from Forge-specific self-registration so the same code could be shared across loaders. No gameplay or settings changes, this is an internal restructuring, not a new feature.
- Fabric/Quilt: Loader 0.19.4 / Fabric API 0.158.0+26.2 : brand new platform support.
- NeoForge: 26.2.0.67 : brand new platform support.
All target Minecraft 26.2. Pick whichever loader you already use the mod behaves the same everywhere.
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:GZ99CgTD:Lgw4wrYU"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GZ99CgTD:Lgw4wrYU"
}

