Tags
Creators
Details
Licensed MIT
Published 3 years ago
Updated 3 months ago
All versions
3.2.0
Release
RegionTeleport 3.2.03 years ago 488
Compatibility
Minecraft: Java Edition
1.20–1.20.2
1.19.x
1.18.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
NOTICE: Spigot Support will be dropped in the near future to take in use things like async teleportation, Kyori Adventure, etc.
New Features
- Four WorldGuard flags have been added!
- player-loot-drop - Stop player loot from dropping on death
- mob-loot-drop - Stop mob loot from dropping on death
- regiontp-on-entry - Teleport a player to one of the specified locations when they enter the region
- regiontp-on-exit - Teleport a player to one of the specified locations when they exit the region
- The regiontp flags works exactly the same as the tp command for spawns, just add the spawns as
spawn1,spawn2as the flag value. This also includes CMI/Essentials addons, ex:ess:spawn1,spawn2
Changes
- Plugin now depends on 1.20.1
- Updated dependencies
- api-version has been changed from 1.13 to 1.18
- Plugin now depends on Paper instead of Spigot (Still works on spigot atm)
- Recoded RegionTeleportCommands
- Split some of the code into their own methods for ease of use with other parts of the plugin
- Removed the two different versions I had for player senders & other senders, there's now only 1 sender.
- All commands should work from anything that can send commands
/regiontp setspawn <name>is now/regiontp setspawn <name> (-x:<x>) (-y:<y>) (-z:<z>) (-w:<world>) (-yaw:<yaw>) (-p:<pitch>)with the variables being optional for players.- If a command like setspawn or tp was sent by a player, they, as before, don't have to enter any coordinates / worlds, but they can now do that if they want to.
- If setspawn is run by a player, the player, if they choose, to include only some of the variables, and the unspecified ones will be grabbed from their location, for example if the player is standing at X 10 Y 50 Z 40, and they specify -x:25 in setspawn, the spawn location will be X 25 Y 50 Z 40.
- Changed some folder & java file names.
- Deleted some unused code
- Made some stuff static
Optional dependencies
Any compatible version
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:Fx7yY5cp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Gaf6ylkx:Fx7yY5cp"
}

