Tags
Creators
Details
1.20.1-0.7.2
Compatibility
Changes
📦 Changelog - Version 0.7.2
🛠️ Fixed: Delivery ID is now correctly sent to the WordPress API (mark-delivered) via ids parameter.
🛠️ Fixed: Token usage is now consistent across all REST calls (fetch + mark delivered).
🛠️ Fixed: Gradle now injects the actual plugin version into plugin.yml using ${version}.
🛠️ Improved: Startup console now dynamically displays the actual plugin version.
🛠️ Improved: Enhanced error handling and debug logging for REST API failures (400, 403, 500).
✨ Added: Support for bulk delivery marking with markAsDelivered(List<Integer>).
✨ Added: Automatic encoding for tokens and delivery IDs in POST body parameters.
✨ Added: More informative startup messages showing API mode, domain, and readiness.
🔐 Token verification is now 100% enforced before delivery updates.
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:t8eLuzvc:ZJqKKaB6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:t8eLuzvc:ZJqKKaB6"
}

