Tags
Creators
Details
Licensed MIT
Published 6 months ago
All versions
3.4.1
Release
EzRTP 3.4.113 hours ago 0
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
Added
- Minecraft
26.2compatibility updates:- added
SULFUR_CAVESto rare-biome defaults/search paths, - updated biome compatibility handling for modern registry-based lookup paths.
- added
Changed
- CI server download resolution migrated to PaperMC Fill API (
fill.papermc.io) and now sends an explicit non-genericUser-Agentheader as required by the service. - Smoke testing workflow expanded from a single Folia target to a matrix that validates:
- latest Folia build, and
- Paper
1.13.xfor earliest supported compatibility coverage.
- Dependency and tooling updates merged via Dependabot:
com.github.ez-plugins:teams-api1.8.0->2.4.0.- GitHub Actions
actions/checkoutv6->v7. - GitHub Actions
DavidAnson/markdownlint-cli2-actionv23->v24.
- Kyori Adventure BOM and related versions moved to
5.2.0for current Paper API compatibility.
Fixed
- GitHub Actions workflow resolver for smoke-test target versions:
- fixed YAML parsing issues in embedded resolver scripting,
- fixed selector propagation into Python resolver invocation,
- fixed mixed-type version sort key handling that could fail on Paper version token comparisons.
- Removed a duplicate stale block in
messages/en.ymlthat produced duplicate-key warnings at startup. - Replaced deprecated
Biome.valueOf/Biome.valuesusage with compatibility-safe registry-backed resolution paths used across biome-related logic.
Optional dependencies
Supplementary resources
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:14xPXPKx:bG1CC3Bs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:14xPXPKx:bG1CC3Bs"
}









