Tags
Creators
Details
0.7.9-main-SNAPSHOT
Compatibility
Changes
✨ New Features & Enhancements
✅ New TPA System (Teleport Requests)
- Added
/tpa,/tpaccept,/tpdenywith full tab-completion support. - Requests are now stored via an abstraction
TpaRequestStorewith two implementations:- LocalTpaRequestStore (in-memory, fast for single-server setups)
- RedisTpaRequestStore (shared across multiple servers, ideal for networks)
- Players can only teleport once the target accepts the request.
- Added configurable TPA timeout (
Config.Tpa.Tpa-duration, default: 30 seconds).
✅ Improved Tab Completion
/tpaccept <player>and/tpdeny <player>now suggest only valid requesters.- Dynamically pulls data from cache/Redis for real-time accuracy.
✅ CacheManager Integration
- Centralized access for all active TPA requests.
- Supports both Redis and Local modes seamlessly.
🔧 Internal Changes
- Refactored
TpaRequestStoreto unify Redis & Local implementations. - Added
getAllTpaSenders()+getTpaTarget(UUID)to simplify request lookups. - Safer cleanup of expired or invalid TPA requests.
- Enhanced Redis handling with UUID-safe storage and retrieval.
🌐 Language Updates
Added new language entries in french.yml, english.yml, and custom.yml:
Tpa.Request-Sent→ "You have sent a teleport request to {player}"Tpa.Request-Received→ "{player} has sent you a teleport request. Use /tpaccept or /tpdeny."Tpa.Request-Expired→ "Your teleport request to {player} has expired."Tpa.No-Pending→ "You have no pending TPA requests."
📌 Notes
- ⚙️ If running in a networked setup, enable Redis in
config.yml. - 🔁 All changes remain backward-compatible.
- 🌐 Update language files manually with
/lang update.
Full Changelog: https://github.com/fuzeblocks/HomePlugin/compare/0.7.8...0.7.9
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:kbERwJ64:h67cPk6G"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kbERwJ64:h67cPk6G"
}

