Tags
Creators
Details
1.0.3
Compatibility
Changes
Bug Fixes Separated global warps from player homes: Warps are now stored in a dedicated warps.yml file via a new WarpsManager class, preventing mixing warps with player homes and enabling global warp management.
Fixed warp cooldown timing: Warp cooldown is now correctly handled in seconds internally and compared against System.currentTimeMillis() in milliseconds, with proper cooldown messages showing time left.
Registered event listeners: Added PlayerEventListener to properly handle PlayerTeleportEvent and PlayerDeathEvent for tracking last player locations used by /back.
New Features Multi-world spawn support: Spawn points can be set and saved per world. /setspawn sets spawn for the current world, and /spawn teleports to the spawn of the player’s current world.
Added /homes command: Lists all homes a player has set.
Added /warps command: Lists all global warps available.
Added /tpdeny command: Allows players to deny incoming teleport requests.
Added tab completion: Commands /home, /delhome, /warp, /delwarp, /tpask, and /tpahere now support tab completion for easier usage.
Added permission nodes for all commands: Each command has a dedicated permission node prefixed with essentials999. for fine-grained permission control.
Async saving of homes and warps: Saving of homes and warps to disk is now done asynchronously to improve server performance.
Improvements Teleport safety checks: Teleports now check if the destination location is safe (not inside blocks) when safe-teleport is enabled in config.
Cooldown feedback: Players receive a message showing how many seconds remain before they can use /warp again.
Improved teleport request management: Teleport requests can be accepted or denied, with appropriate messages sent to both parties.
Cleaned up code structure: Refactored PlayerHomes and WarpsManager classes for clarity and separation of concerns.
Better command usage messages and permission feedback: Commands provide clear usage instructions and permission denial messages.
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:gExGycAJ:waOuCg25"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:gExGycAJ:waOuCg25"
}

