Tags
Creators
Details
1.0.1
Compatibility
Changes
DyRTP 1.0.1
This maintenance release fixes ordinary-player RTP failures, keeps teleportation free without an economy provider and adds shorter commands while preserving DyRTP's command-based experience.
Fixed and improved
- Keep the selected destination chunk loaded throughout warmup. Shared tickets are released after completion, failure, cancellation, reload or shutdown; final terrain and protection checks remain in place.
- Keep RTP free when Vault or a registered economy provider is absent, including when an older configuration still contains a positive price. Reject positive prices and enabling payments until a provider is detected; provider transaction failures still stop paid requests safely.
- Detect economy provider registration changes without requiring payments to be enabled first.
- Add
/dyras a shortcut for/dyrtp, and/dyra <operation>for/dyrtp admin <operation>, with the same permissions and localized TAB suggestions. - Use Turkish
Oto/otoin language labels, help and TAB. Keepotomatikaccepted and update unchanged stock labels without replacing custom translations. - Remove the help command's own descriptive row from the help menu.
- Use
1.0.1for the new tag andDyRTP-1.0.1.jarfor the download, without avprefix. Historical release tags and files remain unchanged.
Verification
90 automated tests passed. Targeted live checks used an actual non-OP Java protocol client on Paper 26.1.2 / Java 25: normal RTP with warmup, /dyr, /dyra permission denial and free RTP with stored paid settings but no Vault/provider. The complete Minecraft/platform range and live economy transactions were not individually retested.
The controlled BetterRTP comparison was repeated for this artifact. Command-to-teleport measurements describe the documented setup, not CPU/RAM usage or a universal speed/safety guarantee.

Comparison method and results · Verification details
Updating
Stop the server, back up the existing JAR and complete plugins/DyRTP folder, replace the JAR with DyRTP-1.0.1.jar, then restart. Keep your existing configuration, translations and player data. Missing defaults are added without resetting custom values. Core RTP needs no other plugin; paid RTP requires Vault and a registered economy provider.
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:9CgVapLR:GIFz4m4f"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9CgVapLR:GIFz4m4f"
}

