Tags
Creators
Details
3.6.5
Compatibility
Changes
[1] The search now learns the terrain of your world and stops re-checking areas it knows are bad. Every generated chunk is scored safe or bad into a coarse per-world map; once an area (like a large ocean) has proven mostly bad, rolls that land there are re-rolled before any chunk is generated. Landing spread stays exactly as configured, avoidance is just a fresh roll of the same shape. Unlike the short-term failed-area memory this learns from successes too and is saved to terrain-memory.dat, so it keeps improving across restarts, the background cache fill teaches it the whole reachable map over time and day two is faster than day one. Areas whose rules change (a biome un-blacklisted) recover on their own. New location_cache.terrain_memory block, on by default. config-version 50.
[2] Paid teleports now always refund when they don't happen. If the cost was taken but the teleport then failed (another plugin cancelled it), the player quit mid-search, or the request was a rejected duplicate, the money was silently gone. All of those refund now.
[3] /rtp nearclaim and /rtp nearplayer go through the same path as every other RTP. nearclaim was using a weaker safety check that could drop you in a claim, in lava, or on powder snow, and both skipped the normal arrival effects; they now get the full biome/region/hazard safety and the same effects, sounds and smooth landing.
[4] Fixed two rare cache races: two players could very occasionally be sent to the exact same block, and a slow background cache-fill on a heavy world could be wrongly restarted and run twice. Also hardened the air-drop parachute against a Folia region-boundary crossing mid-glide.
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:flhsUQKt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:L0rNG1h2:flhsUQKt"
}

