1.0
Compatibility
Changes
Rptback
Rptback is a modern, highly optimized /back plugin built specifically for Folia and Paper (1.20+ / 1.21+) servers. It safely teleports players back to their previous locations or death points without causing any main-thread lag or asynchronous exceptions.
âš Key Features
- ⥠100% Folia Supported: Fully utilizes Folia's
RegionSchedulerandEntitySchedulerfor safe, asynchronous cross-world teleportation and block checking. - đĄïž Smart Safety Checks: Prevents players from teleporting into lava, void, or suffocating blocks. If the original death point is dangerous, the plugin will automatically scan up to a 24-block radius to find the nearest safe landing spot.
- â±ïž Teleportation Warm-up: Configurable teleport delay. If a player moves during the warm-up, the teleportation gets cancelled automatically.
- đŹ Interactive Chat Buttons: When a player dies, they receive a clickable
[Back]button in the chat to easily return to their death point. - đ Multi-Language Support: Fully customizable messages. Comes with built-in English (
en) and Chinese (zh) language files. - đ Priority Override: Automatically overrides the
/backcommand from other plugins (like EssentialsX) to ensure the Folia-safe version is always used.
đ Commands & Permissions
/back- Teleport to your previous location or death point.- Permission:
rptback.use(Default: True)
- Permission:
/rptback reload- Reload the configuration and language files.- Permission:
rptback.admin(Default: OP)
- Permission:
âïž Configuration
Easily toggle between languages and set your desired teleport delay in the config.yml:
Language setting (en or zh)
language: en
Teleport delay in seconds (set to 0 for instant teleport)
teleport-delay: 3
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:EaB1tUWQ:r7vyIzz4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EaB1tUWQ:r7vyIzz4"
}

