Tags
Creators
Details
1.2.4
Compatibility
Changes
What's new
Now works on Minecraft 26.1, 26.2 and 26.3.
Starting in 2026, Minecraft names its updates by year and drop number instead of 1.21.x. The three drops so far:
- 26.1 — Tiny Takeover (March 24, 2026)
- 26.2 — Chaos Cubed (June 16, 2026)
- 26.3 — Wilderness Bound (September 15, 2026)
This update adds support for all three.
- The same file works on both old and new versions. No separate download, nothing to choose.
- Still works on 1.21.x, so you can update now even if your server hasn't moved to 26.x yet.
- Requires Paper.
Heads up if you're moving to 26.x: Minecraft itself now requires Java 25 from 26.1 onwards. Your server will not start on Java 21, regardless of this plugin. On 1.21.x, Java 21 is still fine.
Just replace the old file and restart. Your config, messages and player flight time stay exactly as they are.
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:WjpHQV0s:Q0GPiB2e"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:WjpHQV0s:Q0GPiB2e"
}
