Tags
Creators
Details
All versions
2.1.0
Release
TeleHop 2.1.03 months ago 98
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platform
Paper
Changes
[2.1.0] - 2026-07-13
Added
Redis TLS
redis.ssltoggle inconfig.propertiesto connect to Redis over TLS (rediss)redis.ssl-verifyto control certificate and hostname verificationredis.ssl-ca-certfor self-signed setups (path to a PEM CA certificate)
Destination Ping in RTP GUI
- Region items now show the ping a player will get on the destination server, with the value colour-coded green/yellow/red
- The ping line refreshes twice per second while the menu is open, including while hovering
- Velocity measures proxy-to-backend RTT every 10 seconds and broadcasts it via the new
SERVER_PING_UPDATEpacket - Paper-side
PingServicecaches the RTTs and estimates post-transfer ping from the player's current connection - New
rtp.gui.pingsection inrtp.yml:enabled,proxy-ping - GUI item tooltips hide vanilla attribute/material info (item flags applied)
Fixed
RTP
- The picker GUI closes immediately when a destination is selected, so players can no longer re-click items to restart or stack the warmup countdown
- Cooldown is now consumed when a destination is actually selected, not when
/rtpopens the menu; opening and closing the GUI no longer burns the cooldown - A pending-RTP guard blocks
/rtpand further selections while a warmup or transfer is in flight (newrtp-in-progressmessage in all six languages)
Migration from 2.0.0
- Update the Paper and Velocity JARs together: 2.0.0 jars do not recognise the new
SERVER_PING_UPDATEpacket - Existing servers: add the
rtp.gui.pingsection toconfig/rtp.ymland thertp-in-progresskey to customised language files (or regenerate them); defaults and the English fallback apply otherwise - No database changes
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:cjTmNjaL:KwPZWtLz"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:cjTmNjaL:KwPZWtLz"
}

