Tags
Creators
Details
0.2.1
Compatibility
Changes
Patch on 0.2.0 fixing two production bugs:
-
Discord webhook 429 fix. The 429 rate-limit branch was unreachable (caught earlier by an
if statusCode/100 == 4that disabled the webhook on the first burst). Now: 429 is handled FIRST with proper Discord retry_after parsing + back-off + retry; only OTHER 4xx codes disable the webhook. -
Coalescing window. /fill 8 alternate-current (= 289 chunks) used to produce 289 webhooks → instant rate-limit + ban. Now: events within a 2.5s window sharing (actor, source, dim, target-mode) are batched into ONE message with chunk range + block range + tp-center coords. Plus a true 5 req/s rate (250ms sleep between consecutive POSTs, not just per-drain).
-
Plugin display name now
RedstoneRegionsin /plugins, /version, /pl, etc. — matches the Modrinth title. Wasfolia-redstone-region.
Same feature set as 0.2.0. 14/14 harness still green.
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:3nrWCEFD:IazP6snC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3nrWCEFD:IazP6snC"
}

