1.3.0
Compatibility
Changes
Tidal Commission 1.3.0 — Config Editor, Task Management & Commission Archive
This update focuses on making Tidal Commission much easier to configure for modpack creators. Task definitions have been moved toward a fully config-driven workflow, with an in-game editor, a task management screen, better diagnostics, and a new Commission Archive item for player progression tracking.
Added
-
Added a new in-game task configuration editor for modpack authors.
- Open it with
/tc editor. - Supports editing task source, tier, weight, time limit, short description, and full description.
- Supports clicking items from the inventory to automatically fill requirement or reward entries.
- Supports manually entering item IDs.
- Requirements can now be either item-based or tag-based.
- Rewards remain specific item IDs.
- Newly created tasks are automatically saved under
config/tidalcommission/tasks/editor/. - File names are generated automatically, so players do not need to manually write file paths.
- Open it with
-
Added a new task configuration management screen.
- Open it with
/tc editor manage. - Displays configurable task files from
config/tidalcommission/tasks/**/*.json. - Supports editing existing tasks.
- Saving an existing task now overwrites the original file instead of creating a duplicate.
- Supports deleting task files.
- Deleting a task now requires a second confirmation to prevent accidental deletion.
- Open it with
-
Added a new item: Commission Archive.
- Right-click the Commission Archive to view the player's total completed commission count.
- Added milestone rewards based on completed commission count.
- Players can claim rewards after reaching specific commission completion milestones.
- Milestone rewards are configurable.
- The Commission Archive screen supports multiple pages.
Changed
-
The task system is now config-driven.
- Runtime task pools now only read from
config/tidalcommission/tasks/**/*.json. data/tidalcommission/tasksis no longer used as a runtime task source.- Built-in data tasks are now only used as templates when generating default config tasks for the first time.
- If no task JSON files exist in the config folder, default tasks will be generated automatically.
- If config task files exist but all of them are invalid, they will not be overwritten automatically. A warning will be printed in the log instead, so pack makers can check their configuration files manually.
- Runtime task pools now only read from
-
Improved
/tc doctor.- Now shows the number of config task files.
- Now shows the number of successfully loaded tasks.
- Now shows the number of skipped or failed task files.
- This makes it easier to diagnose task configuration issues in modpacks.
-
Improved the Commission Archive screen display.
-
Improved milestone reward claiming logic.
-
Improved datapack task loading and refresh logic.
-
Improved server-side config synchronization and client/server stability.
-
Improved display compatibility for custom commission and commission management screens.
-
Improved editor layout compatibility for small windows and GUI scale changes.
-
Long file names and long descriptions in the management screen are now automatically truncated to avoid overlapping buttons.
Fixed
- Fixed incorrect parameter order in the Chinese card-flip confirmation text.
- Fixed the editor screen being partially cut off in small windows or after GUI scale changes.
- Fixed editor input contents being lost after scrolling or screen rebuilding.
- Fixed some custom-drawn screens being affected by Minecraft's "Menu Background Blur" setting.
- Fixed unstable behavior in some debug command states.
- Fixed possible display issues caused by data desynchronization in some client/server environments.
Cleanup
- Removed obsolete cost and star-level text remnants from the task editor.
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:9qSE6OU6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MdP0Tf9n:9qSE6OU6"
}

