Tags
Creators
Details
Licensed MIT
Published 2 weeks ago
Updated 3 weeks ago
All versions
v1.2.1
Release
Neoforge 1.21.1 - XP Teleport 1.2.13 weeks ago 19
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Changes
[1.2.1] - 2026-07-10
This release implements command-specific cooldowns and flat rates, reverses the TPAHere payment logic so the summoner pays, and fixes the offline XP leaderboard rendering.
Added
- Command-Specific Cooldowns: Extracted the global cooldown into a command-specific JSON configuration map
cooldownsinconfig/xpteleport.json(defaults:/home= 60s,/rtp= 120s). - Command-Specific Distance Toggles: Added config flags
home_distance_based(default: false),back_distance_based(default: true), anddeath_back_distance_based(default: false) to separate pricing styles for specific teleports. - Location Origin Tracking: [BackManager] now logs whether a back coordinate was generated by player death.
Changed / Fixed
- TPAHere Payment Reversal: Charging now applies to the summoning requester (Player A) instead of the target player (Player B). The target player performs the warmup while the requester pays upon successful completion. Both players receive status notifications.
- XP Leaderboard Improvements:
- Offline players are matched using
.datinstead of.nbtto correctly load profile stats. - The cache is pre-populated synchronously during startup (
ServerStartedEvent) and fallback checks to fix the bug where the leaderboard was empty on first query. - Output display is formatted as a clean plain-text string:
rank. PlayerName levelslevels.
- Offline players are matched using
- Default Flat Costs: Configured
/homeand/backafter death to charge a flat cost of2XP levels by default.
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:mUl318mZ:DRMwpq9o"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mUl318mZ:DRMwpq9o"
}

