Tags
Creators
Details
1.3-SNAPSHOT
Compatibility
Changes
Changelog — 1.3-STABLE
This update introduces a brand-new warp system and a full rewrite of the plugin’s configuration handling. Because of this, all configuration files need to be regenerated, but the new system is cleaner, more reliable, and easier to extend in future versions.
I added the /setwarp and /warp commands, complete with tab-completion for a smoother experience. To access a specific warp, players now need the permission jte.warp.<warpname>, and as always, command permissions follow the format jte.<command>.
A bigger update this time, but one that greatly improves structure and usability going forward.
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:5VmClCa3:50wQ5Q4z"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5VmClCa3:50wQ5Q4z"
}

