1.1
Compatibility
Changes
-
Fixed safe-mode timing: previously, post-processing was triggered in the same tick after PlayerPortalEvent, which meant that with cancel-portal-exit: false, it could be executed before the actual teleport.
-
Teleportation with cancel-portal-exit: true has been moved to a “plugin” cause (TeleportCause.PLUGIN) so that other plugins/anti-cheats can distinguish this teleportation more correctly.
-
The unreliable check unstableMessage.equals(Component.empty()) has been removed: now an empty/blank message correctly disables message sending.
-
The platform is no longer set to “always”: previously, createPlatform() was called every time safe-mode: true, even if the player was not stuck.
-
Added protection against teleportation to the roof of the Nether: random Y and point search are limited to a safe maximum (below the bedrock layer), so the coordinate will not go into the roof area.
-
Improved base point selection
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:VubTUIKh:JCKYgrpR"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VubTUIKh:JCKYgrpR"
}

