Tags
Creators
Details
2.0.2
Compatibility
Required content
Changes
Config Overhaul & Broadcast Types Config format changed from JSON → YAML. All config files (chatmod.yml, messages.yml, placeholders.yml, predefined_broadcasts.yml) are now YAML with full #comment support. Existing JSON configs are automatically migrated on first launch — your data is not lost.
Predefined broadcasts now support all 4 display types. Each entry in predefined_broadcasts.yml can now set type: CHAT, type: ACTION_BAR, type: TITLE, or type: BOSSBAR, with the matching options (duration_seconds, boss_bar_color, boss_bar_overlay) for title and bossbar entries.
/cm bcnow now supports all 4 broadcast types. Syntax changed to /cm bcnow <chat|title|actionbar|bossbar> <message>. Examples: /cm bcnow actionbar Server restarts in 5 minutes! /cm bcnow title Welcome to the server!. Works with the scheduler too: /cm time 10m often 3 bcnow title Event Starting!
Optional dependencies
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:UeyZY1Lc:Gif6rhb2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:UeyZY1Lc:Gif6rhb2"
}

