All versions
1.0.2
Release
MightyRTP 1.0.2last year 39
Compatibility
Minecraft: Java Edition
1.21–1.21.8
1.20.x
1.19.x
1.18.x
1.17.x
Platforms
Paper
Purpur
Changes
[1.0.2] - 2025-01-20
Added
- Multiverse-CommandDestination compatibility - Full integration with portal systems using [world] arguments and console command support for
/rtpcommand - World-specific RTP functionality -
/rtp %player% [world]to teleport to specific worlds - New permission
mightyrtp.rtp.worldfor world-specific teleportation - Enhanced command usage with world parameter support
Changed
- New config settings Delete old config.yml and generate a new one if you're updating from a previous verison
- Enhanced plugin description to mention Multiverse-CommandDestination compatibility and world support
- Improved command usage documentation
- Refactored RTPCommand for better console/player command handling
- Console commands now work seamlessly with Multiverse portals, (Multiverse-CommandDestination required)
Technical
- Added
executeRTP()method for shared teleportation logic - Added
executeRTPInWorld()method for world-specific teleportation - Console execution detection and handling
- Portal command format detection (
args[0] == "player") - World parameter handling and validation
- Cooldown bypass for console commands
- Permission bypass for console commands
- Performance optimizations: Reduced max attempts, faster chunk loading, fast mode for console
- Fast mode: New fast mode that skips chunk loading for maximum speed
- Fast mode configuration: Configurable fast mode settings for better performance
- Fast mode safety levels: Configurable safety levels (1=basic unsafe blocks check, 2=+air above, 3=full safety)
- Console title suppression: Console RTP commands no longer show titles to players (configurable)
- Maintained full backward compatibility
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:p0xDIiQA:RJEUqmaQ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:p0xDIiQA:RJEUqmaQ"
}

