Tags
Creators
Details
4.0.0
Compatibility
Changes
IMPORTANT INFO
This version is close to a full rewrite of the entire plugin, so a lot of things are different in this version than previous ones!
Also, even though I have tested it extensively, due to this being a large update, there might be bugs that snuck through my testing. So if you find any, please report them on github.
Changes:
-
Teleport command has been changed to:
/regiontp tp "region1 region2 ..." "spawn1 spawn2 ..." (-s)/regiontp tp <world> "region1 region2 ..." "spawn1 ..." (-s)
The quotes are only needed for multiple regions or spawns.
/regiontp tp region1 spawn1works aswell. -
Clear command has been changed to:
/regionclear "region1 region2 ..." "option1 option2 ..." (-s)/regionclear <world> "region1 region2 ..." "option1 ..." (-s)
Quotes are here also only needed for multiple regions or options.
The options which you can provide a list of your own, specific, named-only & items, work the same, with each type being split by a comma. Example:/regionclear __global__ "specific:wolf,cow named-only:dave" -
Setspawn command has been changed to
/regiontp setspawn <name> (x y z) (yaw pitch) (world) -
/regiontp spawnlist has been changed to /regiontp list (page). The permission has also been changed to regionteleport.command.list.
-
/regiontp list is now split into pages, and you can easily teleport to each spawn by clicking on it.
-
Took in use CommandAPI as the command framework instead of bukkit commands. This also means all commands are now brigadier commands.
-
Removed the lang file because I didn't see the point in having it.
-
The plugin is now using Papers teleportAsync to teleport players.
-
Java 21 is now required.
-
Changed the API version to 1.20.
Optional dependencies
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:Gaf6ylkx:eUPCjYdI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Gaf6ylkx:eUPCjYdI"
}

