All versions
1.
2.
1.
2.
2.0
Release
RTPQueuePro 2.02 years ago 832
Compatibility
Minecraft: Java Edition
1.21–1.21.4
Platforms
Bukkit
Paper
Spigot
Changes
Commands
1. /rtpqueue
- Description: Join or leave the teleport queue
- Usage:
/rtpqueue - Permission:
rtpqueue.queue - Behavior:
- If not in queue: Adds player to queue and sends waiting message
- If in queue: Removes player from queue and sends leave message
2. /rtpqreload
- Description: Reload the plugin configuration
- Usage:
/rtpqreload - Permission:
rtpqueue.reload - Behavior: Reloads all configuration settings and restarts queue tasks
Permissions
1. rtpqueue.queue
- Description: Allows players to use the
/rtpqueuecommand - Default: Not set
- Recommended for: All players who should be able to use the random teleport queue
2. rtpqueue.reload
- Description: Allows players to reload the plugin configuration
- Default: op
- Recommended for: Server administrators only
Configuration Features
World Settings
- Target world configuration
- World border support
- Custom boundary settings
Teleport Settings
- Maximum teleport attempts
- Minimum and maximum player distance
- Queue timeout system
- Safe block configuration
- Minimum height check
Customizable Messages
- Queue join/leave notifications
- Teleport success messages
- Error messages
- Timeout notifications
Safe Teleportation System
The plugin includes a sophisticated safe teleportation system that:
- Checks for safe landing blocks
- Ensures proper distance between teleported players
- Respects world borders
- Performs async processing to prevent server lag
- Validates locations before teleporting
Technical Details
- Async processing for performance
- Concurrent queue management
- Built-in timeout system
- World border integration
- Configurable safe blocks list
- Event handling for player disconnects
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:4MCvdYqI:zjAfEdk7"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:4MCvdYqI:zjAfEdk7"
}
