Tags
Creators
Details
1de2601
Compatibility
Changes
Fix LimboAPI login injection on Velocity-CTD (DEFAULT_PERMISSION_RESOLVER fallback) (#236)
Velocity-CTD does not expose ConnectedPlayer.DEFAULT_PERMISSIONS (it uses DEFAULT_PERMISSION_RESOLVER instead), which caused LoginTasksQueue static initialization to fail with NoSuchFieldException during player connect.
Update LoginTasksQueue to prefer DEFAULT_PERMISSIONS when present (standard Velocity), and when absent, reflect DEFAULT_PERMISSION_RESOLVER and wrap it into a PermissionProvider so PermissionsSetupEvent can still run.
This restores LimboAPI login injection compatibility with Velocity-CTD.
Co-authored-by: gbpii gbpii@users.noreply.github.com
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:TZOteSf2:d2tbmo9O"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TZOteSf2:d2tbmo9O"
}

