Tags
Creators
Details
1.0.0
Compatibility
Changes
ColorApocalypse v1.0.0 - Initial Release
The world is losing its colors, and it's not giving them back. A wheel spins across your XP bar at random intervals, whatever color it lands on gets wiped from existence: blocks, mobs, and item drops alike.
Features
- Color wheel mechanic : a synced multiplayer countdown -> spin -> reveal sequence, driven by the XP bar, with matching sounds and a full-screen color reveal.
- Block destruction : every block tied to the eliminated color (wool, concrete, terracotta, stained glass, naturally colored blocks like grass/leaves) is destroyed around every player, within a configurable radius.
- Mob death : mobs of the eliminated color (sheep, wolves, llamas, tropical fish, painted shulkers, and dozens more) die instantly.
- Item destruction : dropped items of that color are destroyed on the spot; optionally (off by default) the same applies to items sitting in players' inventories and equipment.
- Automatic & manual triggers : the wheel spins on its own based on world difficulty, or an operator can force a draw anytime with
/colorapocalypse start. - Self-sustaining cycle : once every color has been eliminated, the pool refills automatically and the apocalypse starts over, no manual reset required.
- Fully configurable ; destruction radius, per-difficulty timers, and every destruction category can be toggled via
/colorapocalypse settings. - Localized in 35 languages : every player sees titles, subtitles, and command feedback in their own client language.
Commands (OP only)
/colorapocalypse start | status | reset | pause | settings <parameter> <value>
Requirements
Minecraft 26.2, Forge 65.1.2
Full details in the README.
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:YeanmrtZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:GZ99CgTD:YeanmrtZ"
}

