Tags
Creators
Details
3.8.1
Compatibility
Changes
[1] Fixed players landing at the same spots again and again. When the location cache had no ready spot, the spot a search found for one player was also stored in the cache and given to the next player, so two players often arrived on the exact same block. Every spot now goes to one player only.
[2] Added custom_worlds.<world>.attempts to set how many spots RTP tries in a single world, for example only in the End or in a sky-island world. It overrides settings.attempts, attempts_nether and attempts_end for that world. Queue (matchmaking) teleports now use these values too instead of always 25.
[3] Fixed VOID worlds finding nothing unless they were also listed under location_cache.worlds. A world set to VOID in world_types now generates the chunks a search needs on its own. A generate_chunks value you set for the world still wins.
[4] Fixed air drops into VOID worlds never landing. void_world.platform_block was skipped for /rtp air, so players glided down to empty void and kept falling. The platform is now placed under the landing spot of an air drop as well.
[5] Flight now stays off for the whole air drop. If another plugin turns flight back on during the drop (for example staff running /fly <player>), it is switched off again right away and given back on landing. Commands in air_rtp.glide.blocked_commands are also blocked in their namespaced form, such as /essentials:fly.
[6] Fixed every message turning into "Message not found" after a mistake in messages.yml, for example a ' inside a value wrapped in single quotes. The console now shows the line and column of the mistake, and JustRTP keeps sending the default messages (or the last working file after /rtp reload) until it is fixed. A key missing from the file, the prefix included, falls back to its default text.
[7] The message prefix is now rendered on its own, so a tag left open in the prefix no longer changes the colours of the message after it. Legacy colour codes such as &6, &l, &#ff8800 and §6 work in messages.yml. Before, a § code in the prefix made /rtp fail with "An unexpected error occurred". The prefix in the /rtpzone setup prompts was shown as raw tags and is now formatted.
[8] Config version is now 58. Existing values are preserved during the update.
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:pt1SQTRZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:L0rNG1h2:pt1SQTRZ"
}

