Links
Tags
Creators
Details
1.4.2
Compatibility
Changes
-
Fixed permission check just... not existing? I must of been tired when I wrote/pushed that, jeez.
-
Also, instead of checking if a user is an operator for using commands like wconfig, I added zoink.waypoints.admin as a new permission that must be set to someone if they want to use those commands. Though, in testing, server operators can still use these commands without being granted that permission, which I assume is how that works.
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:egQRTISK:pfyDKfWa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:egQRTISK:pfyDKfWa"
}

