
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.0
Compatibility
Changes
Added
- 🛡️ Staff verification — optional approval flow where requests wait for a staff ✅/❌ before being whitelisted (
staff-role-id). - ⏳ Pending/approved/denied status embeds in Discord.
Changed
- ⬆️ Paper API bumped to
26.1.2(new year-based versioning, after 1.21.11). - ☕ Java 21 → Java 25 — now compiles to Java 25 bytecode for Minecraft 26.1+.
- 🌐 All messages and logs translated from German to English.
Notes
- The Java 25 bytecode means the plugin targets MC 26.1+ servers; it will not load on older 1.21.x (Java 21) servers.
- Works on Paper, Spigot and Bukkit — uses only standard Bukkit API.
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:5dF1FQL6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:BpsEaSBS:5dF1FQL6"
}
