Tags
Creators
Details
Licensed Apache-2.0
Published 7 months ago
Updated 18 hours ago
All versions
1.5.0
Release
1.5.02 months ago 947
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
DonutRTP v1.5.0
Bug Fixes
- RTP zone no longer cancels when you jump. The warmup countdown now tracks the height where it started, so jumping in place (or any vertical-only movement) keeps the countdown running. Walking out of the zone still cancels as before.
- "Failed to find a safe location" is far less frequent. The surface finder had an off-by-one that placed the player's feet inside the ground block, causing ordinary flat terrain to be rejected. It now scans downward from the true surface (ignoring leaf canopies) and correctly lands players on solid ground.
Behaviour Notes
rtp-zone.countdown.cancel-on-movenow only reacts to horizontal (walking) movement. Jumping never counts as moving. Leaving the zone always cancels regardless of the setting.- Surface scanning uses
MOTION_BLOCKING_NO_LEAVESplus a short downward window, improving success in forests, snowy biomes, and on carpets/slabs.
Compatibility
- Same loaders as 1.4.0 (Paper / Folia / Purpur family, api-version 1.20). Folia-safe: safe-location search and per-player countdowns still run on the correct region/entity threads.
Upgrade Notes
- Replace the DonutRTP jar with 1.5.0. Keep your existing
plugins/DonutRTP/folder. - No config changes are required. The
cancel-on-movecomment was clarified but the key and default (false) are unchanged. - If you previously saw frequent "no safe location" errors, verify your world
radiusandmin-ystill make sense; the finder is now more reliable within those bounds.
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:pxKMPaTo:Auyog0rF"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pxKMPaTo:Auyog0rF"
}

