Creators
Details
2.0.0
Compatibility
Changes
WebConnector 2.0.0
WebConnector 2.0 adds a public Java API and a shared action service, persistent operations with idempotency keys, scoped authentication, typed validation, and signed webhook delivery with retries.
- One Java 17-compatible JAR targets Paper 1.20.1–26.2; 26.3 compatibility is experimental.
- API keys support names, expiry, action scopes and permissions, with IP/CIDR rules and bounded request/operation limits.
- HTTP clients can submit actions, retain request/operation IDs and poll asynchronous results.
- Idempotency reservations survive restarts. Interrupted work is recorded for reconciliation instead of being automatically repeated.
- Java plugins can register private actions, explicitly publish HTTP endpoints and emit webhook events through Bukkit ServicesManager.
- English documentation, Russian guides, OpenAPI, Java/Skript examples and a Paper smoke-test harness are included.
Upgrade
Version 1 configuration requires migration. Empty secrets, unrestricted JSON interpolation and unrestricted file deletion are no longer accepted. The old configuration is left unchanged. Read the migration guide.
The default configuration binds to localhost, generates a private secret and enables only ping. Shutdown and file deletion remain opt-in. Timeouts and command failures can leave partial external effects; retain the original idempotency key and reconcile before creating a new operation.
The automated suite uses real HTTP requests and mock webhook receivers across the 1.20.1/1.20.6/1.21.11/26.2/26.3 API matrix. API/runtime tests do not certify every live Paper or third-party Skript addon combination; see testing.
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:wVO4hI50:pwvAhxCB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:wVO4hI50:pwvAhxCB"
}

