Tags
Creators
Details
1.20.1-0.7.4
Compatibility
Changes
Changelog – Version 1.20.1-0.7.4
🛠️ Changed: Reworked permission handling for /wsl command to allow non-OP player usage.
🆕 Added: New permission woostorelink.wp-link for /wsl wp-link (email) command.
🆕 Added: New permission woostorelink.wp-verify for /wsl wp-verify (code) command.
🔐 Security: Introduced permission checks in command logic to prevent unauthorized access.
🧩 Integration: Improved compatibility with LuckPerms – full permission control now possible without OP status.
🐛 Fixed: Issue where non-OP players received a “command not recognized” error when using linking commands.
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:t8eLuzvc:IQ1T40lC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:t8eLuzvc:IQ1T40lC"
}

