1.4.0
Compatibility
Changes
Tidal Commission 1.4.0 😋
Stage-Based Commissions
-
Added a player stage system. Commissions can now appear or remain hidden based on each player’s current progression.
-
Tasks now support an optional
stage_rulesfield, including:- Require all specified stages
- Require any specified stage
- Exclude players with specified stages
- Adjust task weights based on player stages
-
Added new administrator commands:
/tc stage add/tc stage remove/tc stage list/tc stage clear
-
Player stage data is saved on the server and persists after leaving the world, rejoining, dying, and respawning.
-
Stage progression can be controlled directly through KubeJS, FTB Quests, or datapack commands.
Improved Configuration and Diagnostics
- Added
/tc doctorfor quickly checking task counts, source weights, configuration loading, and invalid rules. - Added
/tc doctor <player>to inspect which tasks a specific player is currently eligible to receive. /tc reloadnow reports skipped configurations, sources with no available tasks, and impossible stage rules.- The task editor now preserves existing
stage_ruleswhen saving, so manually written stage configurations will no longer be overwritten.
Stability Improvements and Task Fixes
- Fixed the resource directory used by built-in tasks, allowing default tasks to be discovered and loaded correctly.
- The Gray Organization music disc commission now uses the general music disc tag, allowing more music discs to be submitted.
- The beginner guide notification is now shown only once and will no longer reappear after death and respawn.
- Commission board state is now preserved after death and respawn.
- Removed unused legacy resources.
Use the following directory for custom tasks:
data/<namespace>/tidal_commission_tasks
The stage_rules field is optional. Existing tasks without this field will continue to work exactly as before.
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:MdP0Tf9n:BeJwfzZV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MdP0Tf9n:BeJwfzZV"
}

