Tags
Creators
Details
Licensed MIT
Published 6 months ago
All versions
1.3.0
Release
EzRTP 1.3.05 months ago 44
Compatibility
Minecraft: Java Edition
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
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
1.7.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
New features in EzRTP 1.3.0
##⚡ Smart Pre-Caching
- Locations are now pre-cached per biome to minimize RTP failures and improve performance.
- Per-biome configuration added to customize the number of pre-cached locations.
- Graceful fallback logic when pre-cached locations are unavailable to avoid player frustration.

🌍 Heatmap Visualization
- Added the /rtp heatmap command to analyze RTP location data visually: Displays RTP density patterns in a heatmap-style visualization on an in-game map.
- Heatmaps automatically render using Minecraft maps and are handed to the player upon execution.
- Option to generate heatmaps by biome with /rtp heatmap <biome> or save as .png files for external usage with /rtp heatmap save.

📊 Improved Statistics
- Updated /rtp stats command with detailed biome-specific statistics: Displays total RTP attempts, success rates, failures, and average teleport times.
- Shows stats like cache hits, biome success rates, and total biome finds.
- Filters out unrelated biome failure logs for clearer representation of requested biome data.
🛠️ Telemetry and Debugging Enhancements
Developers can access detailed logs (via debug mode):
- Including cache hits/misses, teleport timings, biome RTP attempts, and fallback usage details.
- Provides stack traces for pre-caching issues or RTP failures.
💬 Enhanced Messaging System
- Improved RTP status messages with dynamic placeholders like <target-biome> or <location-count> make the user experience more engaging and informative.
- Set to enabled by default but is fully configurable for advanced users.
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:39c5rCBY"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:14xPXPKx:39c5rCBY"
}

