Tags
Creators
Details
3.3.5
Compatibility
Required content
Changes
this update fixes a placeholder bug that prevented some scheduled tasks from ever resuming, adds a configurable task-expiry timer, and redesigns the admin CLI around resources with consistent rendering across console and in-game chat.
so whats new or fixed:
scheduled tasks
- fixed
${arg}placeholders inexecutetarget IDs not being resolved at queue time, so affected tasks could never match a connected client and never resumed - new
tasks.expire-afterconfig option (seconds; default 86400, 0 disables); expired tasks are pruned on load and on the 5-minute save tick - tasks left over with unresolved
${...}placeholders from earlier versions are dropped on load with a warning
admin commands
- redesigned the
/cbtree by resource:/cb script list | show <name> [group] | enable <name> | disable <name>/cb task list | clear <id>/cb client list | ping [id] | players <id>/cb config show [section] | reload
/cb script show <name>opens a clickable section navigator (permissions, register, defaults, args, commands); pass a group to drill into just that group as a syntax-highlighted yaml card/cb script enable|disable <name>edits theenabled:line of the matching yaml file in place (comments preserved) and re-pushes registrations to connected clients/cb config showmirrors the same summary + sections layout; drill into a section via tab-completion or by clicking it in chat- every argument-taking subcommand has live tab-completion now (script names, script groups, task ids, client ids, config keys)
rendering
- single
Reportbuilder drives every command's chat output, so kvs, section headers, bullets, list items, action buttons, and pagination look the same everywhere DebugPrinterexposes genericprintRecord,printRecordOverview, andprintListso any record renders as the same yaml card the old/cb scriptsview used
removed
/cb scripts,/cb tasks,/cb list,/cb ping- replaced by the resource-scoped forms above (no backwards-compat aliases on v3)/cb task show <id>and/cb client show <id>- their list views already show everything useful, no point duplicating
latest commit: 76edfda
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:wIuI4ru2:UNCJoK0T"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wIuI4ru2:UNCJoK0T"
}

