Links
Tags
Creators
Details
2.2.0
Compatibility
Required content
Changes
Support scheduling commands with confirmation and introduce customizable themes. ShellCommand: add pending schedule fields, prompt for confirmation before scheduling, implement startSchedule to run commands after a delay while suppressing duplicate confirmations. ModConfig: add customPrefix/custom color fields. ConfigManager: add color-name -> code mapping and resolveColor helper, apply/save/load theme helpers, always convert color names to codes when saving, and build Theme from configurable fields; adjust default prefixes. ModConfigScreen: add color help text, save hook to persist current theme, UI to select/save themes and customize prefix/colors. Overall: enables user-editable theme colors (by name or § code) and confirmed scheduled command execution.
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:d9Zeqv5x:KLRYtixS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:d9Zeqv5x:KLRYtixS"
}

