All versions
1.7.0
Release
Tidal Commission 1.7.04 days ago 55
Compatibility
Minecraft: Java Edition
1.21–1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
# Tidal Commission 1.7.0
## New
- Added **Task Lines**, allowing commissions to form progression chains with shared progress tracking.
- Commissions can now require one or more **prerequisite commissions** before becoming available.
- Added two unlock behaviors for follow-up commissions:
- **Random Pool**: Joins the normal pool and follows existing source, tier, and weight rules.
- **Priority**: Appears as soon as a regular slot is available, or waits until one opens.
- Added a **Task Line Editor** for creating and managing task lines and their member commissions.
- Added a **Commission Relations** screen for viewing direct prerequisites and follow-ups.
- Added the **Shipyard Restart Plan** example task line, featuring branches, multiple prerequisites, and priority follow-ups.
- `/tc doctor` now detects missing prerequisites, self-dependencies, and dependency cycles.
## Changes & Fixes
- Pending priority commissions are now saved with the player's commission board and persist after rejoining.
- Existing commissions and worlds without task line data remain compatible with 1.7.0.
- Upgrading only adds the example progression links to unmodified built-in shipyard commissions, with backups created beforehand.
- Customized commission files from modpacks will not be overwritten.
- The commission tracking HUD is now disabled by default for new players and after restoring default settings.
- Empty task line JSON files are no longer loaded.
- Added Wiki documentation for task lines, prerequisites, and chained commission progression.
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:dzuyvD21"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MdP0Tf9n:dzuyvD21"
}

