
Whitelister
Manage your Minecraft whitelist directly through Discord. Players can be whitelisted by simply typing their name in a designated Discord channel. The bot responds with emoji reactions to keep the channel clean. Features include per-user whitelist limi
1.1.1
Compatibility
Changes
Bugfix release for Minecraft 1.21.x servers (Java 21). Bedrock support is only available in 1.2.0+ (MC 26.x).
Targets: Paper 1.21.11 ยท Fabric 1.21.10 ยท NeoForge 1.21.1
Fixed
- ๐ NeoForge: players were added with a random UUID, so they could not join and
!removedid nothing. The real UUID is now looked up. - ๐ฆ NeoForge: the mod JAR did not contain JDA, so the bot could not start. JDA is now bundled via Jar-in-Jar.
- โ Fabric: the bot always reacted with โ , even for names without a Minecraft account. It now reacts with โ if the player could not be whitelisted.
- ๐๏ธ Paper: users who removed their last player stayed in
whitelist-data.yml.
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:BpsEaSBS:rELAjaIr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BpsEaSBS:rELAjaIr"
}
