Tags
Creators
Details
2.4.0
Compatibility
Changes
[+] You can now add actions and conditions per spawn in their respective config file (data/spawns), in a next update I will do the same for lobbies
[+] Added autocompletion in the chat tab for the /spawn and /delspawn commands
[+] Added the /spawns command to see the list of available spawns
[+] Added an option to disable changelog notifications in the main config
[+] Added the possibility to import warps from essentials
[+] Added the /deluxeteleport import <plugin> all subcommand (to import all data from a plugin)
[/] Now if a message is empty it will not be sent (before I sent the prefix and the empty message)
[/] Some other minor tweaks
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:VHIryd91:aooapSpt"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:VHIryd91:aooapSpt"
}

