Tags
Creators
Details
1.20.1-0.7.0
Compatibility
Changes
Changelog - Version 0.7.0 Beta Release
π Added /wsl wp-link (email) to allow players to link their Minecraft account to a WordPress email.
π Added /wsl wp-verify (code) to verify a linking code sent via email.
β Ensured that each Minecraft account can only be linked to one email.
β Ensured that email verification is required before linking.
π§ Account linking is now persistent and synced with WordPress user meta.
π Improved security on REST requests.
β οΈ Better error handling and messaging for failed verifications and duplicates.
π‘ Added API integration to communicate with WordPress plugin REST endpoints.
π /wsl checkplayer and /wsl status improved with better feedback.
β Now fully respects WooStoreLink WordPress token security.
π§ͺ Compatibility checked with Spigot 1.20+.|
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:1a9zzSK0"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:t8eLuzvc:1a9zzSK0"
}

