Tags
Creators
Details
3.8.0
Compatibility
Changes
[1] Fixed respawn RTP not working on Folia. Folia does not call the respawn events, so respawn_rtp never ran there. Players on Folia are now teleported once after they respawn, the same as on Paper. The option is in config.yml under respawn_rtp.
[2] Fixed cross-server RTP ignoring the destination server's radius. The lobby sent its own world radius with every request, so a destination set to max_radius: 2500 could place players more than 10,000 blocks out. The lobby now only sends a radius the player typed or one set by their permission group, and the destination server caps every incoming radius to the largest max_radius it allows for that world.
[3] Added a console warning when another plugin takes /rtp. After startup JustRTP names the plugin that owns /rtp, /jrtp, /wild or /randomtp. Set the new force-claim-aliases: true in commands.yml to let JustRTP take these commands back. Aliases set in the server's own commands.yml are never overridden, and /justrtp:rtp always reaches JustRTP.
[4] Fixed RTP GUI world buttons being hidden behind decoration items. A button in a slot that is also listed under decoration (for example slot 26) is now shown.
[5] Fixed a single invalid material stopping /rtp gui from opening. Blocks without an item form, such as WATER, are now shown as their item. Material names work in any case and with "minecraft:", and unknown names are logged with the menu entry and the name. GUI entries for worlds that are not loaded are logged as well.
[6] "Could not find a safe location" now explains the cause. When most attempts fail for one reason (no solid ground in a void or sky-island world, ungenerated chunks, excluded biomes, water or lava, protected regions), the console names the settings to change, and players with justrtp.admin see the same hint in chat. The cache pause warning includes the reason too.
[7] Added void_world.platform_block, off by default. In worlds set to VOID in world_types, a small platform of this block is placed under a player who would otherwise land with nothing below.
[8] Removed the unused PaperLib library from the plugin.
[9] Config version is now 57, messages version 30 and commands version 5. Existing values are preserved during the update.
On networks, set custom_worlds.<world>.max_radius on each destination server. If a rank should reach further on a destination server, add that permission group with its max_radius to the destination server's config as well.
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:qkAWzMdC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:L0rNG1h2:qkAWzMdC"
}

