Tags
Creators
Details
3.6.1
Compatibility
Changes
[1] Added a landing-distance message. After a random teleport JustRTP now tells you how far you landed from the world centre in straight-line blocks, so a /rtp <min> <max> result reads as in-range at a glance even when a single coordinate looks small (the distance is the diagonal, so X=-2880 Z=-13601 is 13903 blocks out and correctly inside a 10000-15000 request). It is on by default and configurable under effects.arrival_distance (turn it off or reword it), and the new <distance> placeholder also works in the title, action bar, boss bar and chat message if you would rather show it inline.
[2] Cross-server teleports use the cache now. A /rtp to another server used to always do a full live search on arrival, which was the slowest teleport of all. The destination server now serves it from that world's ready-location cache when it can, so arriving is close to instant. Falls back to a live search exactly as before when the destination world is not cached.
[3] Custom-radius teleports keep a small results pool. A /rtp <min> <max> whose band does not line up with the background cache used to search live every time. Now each result is remembered in a tiny per-world pool (separate from the normal cache, so it never affects plain /rtp), and a repeated or overlapping band is served from it instantly next time. Size is location_cache.custom_pool_size. For a fixed hot band (a rank's radius, a set warp), matching that world's fill_min_radius/fill_max_radius to it and pre-generating the ring still makes every request an instant hit.
[4] Matchmaking and RTP-zone group teleports use the cache too. The shared landing spot they pick for the group is a normal world-centred search, so it now serves from the cache like any other /rtp instead of always searching live (the individual spread around it still searches live, since that is centred on the group).
[5] Fixed the cache growing larger than needed. A custom-radius request that checked and put back a ready spot was being counted as if that spot had been used, which inflated the demand signal the smart cache sizes itself from. Only spots actually handed to a player count now.
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:L0rNG1h2:epNTWaoi"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:L0rNG1h2:epNTWaoi"
}

