ВЕРСИИ (15)

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 `!remove` did 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`.

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 `!remove` did 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`.

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 `!remove` did 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`.

### Added - 📱 **Bedrock support (Geyser + Floodgate)** — prefix a gamertag with `.` (configurable via `bedrock.prefix`) to whitelist Bedrock players, e.g. `.Steve` or `.Cool Guy`. - 🔎 Gamertags are resolved to their Floodgate UUID through the GeyserMC Global API — no Floodgate dependency needed. - 🕒 Bedrock players unknown to the API are reserved and whitelisted automatically on their first join. - 🧩 Floodgate is detected (optional) and its `username-prefix` is checked against the configured prefix. ### Changed - ⬆️ **Minecraft 26.3** for all platforms: Paper `26.3.build.178`, Fabric (Loader `0.19.5`, API `0.162.0+26.3`) and NeoForge `26.3.0.76` — all on Java 25. - 🧵 Fabric moved from Yarn to Mojang mappings (Loom `1.18`, Gradle `9.7.1`); NeoForge moved to ModDevGradle. - 🗂️ The 1.21.x builds live on in the `1.21.x` branch. ### Fixed - 🐛 NeoForge whitelisted players with a random UUID, so they couldn't join and `!remove` did nothing. - 🐛 NeoForge JAR didn't bundle JDA — now included via Jar-in-Jar. - 🐛 Fabric always reacted ✅, even if the name didn't exist. - 🐛 Removed users stayed in `whitelist-data.yml` after their last player was removed (Paper). - 🔒 NeoForge config is no longer a synced config, so the bot token is never sent to clients.

### Added - 📱 **Bedrock support (Geyser + Floodgate)** — prefix a gamertag with `.` (configurable via `bedrock.prefix`) to whitelist Bedrock players, e.g. `.Steve` or `.Cool Guy`. - 🔎 Gamertags are resolved to their Floodgate UUID through the GeyserMC Global API — no Floodgate dependency needed. - 🕒 Bedrock players unknown to the API are reserved and whitelisted automatically on their first join. - 🧩 Floodgate is detected (optional) and its `username-prefix` is checked against the configured prefix. ### Changed - ⬆️ **Minecraft 26.3** for all platforms: Paper `26.3.build.178`, Fabric (Loader `0.19.5`, API `0.162.0+26.3`) and NeoForge `26.3.0.76` — all on Java 25. - 🧵 Fabric moved from Yarn to Mojang mappings (Loom `1.18`, Gradle `9.7.1`); NeoForge moved to ModDevGradle. - 🗂️ The 1.21.x builds live on in the `1.21.x` branch. ### Fixed - 🐛 NeoForge whitelisted players with a random UUID, so they couldn't join and `!remove` did nothing. - 🐛 NeoForge JAR didn't bundle JDA — now included via Jar-in-Jar. - 🐛 Fabric always reacted ✅, even if the name didn't exist. - 🐛 Removed users stayed in `whitelist-data.yml` after their last player was removed (Paper). - 🔒 NeoForge config is no longer a synced config, so the bot token is never sent to clients.

### Added - 📱 **Bedrock support (Geyser + Floodgate)** — prefix a gamertag with `.` (configurable via `bedrock.prefix`) to whitelist Bedrock players, e.g. `.Steve` or `.Cool Guy`. - 🔎 Gamertags are resolved to their Floodgate UUID through the GeyserMC Global API — no Floodgate dependency needed. - 🕒 Bedrock players unknown to the API are reserved and whitelisted automatically on their first join. - 🧩 Floodgate is detected (optional) and its `username-prefix` is checked against the configured prefix. ### Changed - ⬆️ **Minecraft 26.3** for all platforms: Paper `26.3.build.178`, Fabric (Loader `0.19.5`, API `0.162.0+26.3`) and NeoForge `26.3.0.76` — all on Java 25. - 🧵 Fabric moved from Yarn to Mojang mappings (Loom `1.18`, Gradle `9.7.1`); NeoForge moved to ModDevGradle. - 🗂️ The 1.21.x builds live on in the `1.21.x` branch. ### Fixed - 🐛 NeoForge whitelisted players with a random UUID, so they couldn't join and `!remove` did nothing. - 🐛 NeoForge JAR didn't bundle JDA — now included via Jar-in-Jar. - 🐛 Fabric always reacted ✅, even if the name didn't exist. - 🐛 Removed users stayed in `whitelist-data.yml` after their last player was removed (Paper). - 🔒 NeoForge config is no longer a synced config, so the bot token is never sent to clients.

### Added - 📱 **Bedrock support (Geyser + Floodgate)** — prefix a gamertag with `.` (configurable via `bedrock.prefix`) to whitelist Bedrock players, e.g. `.Steve` or `.Cool Guy`. - 🔎 Gamertags are resolved to their Floodgate UUID through the GeyserMC Global API — no Floodgate dependency needed. - 🕒 Bedrock players unknown to the API are reserved and whitelisted automatically on their first join. - 🧩 Floodgate is detected (optional) and its `username-prefix` is checked against the configured prefix. ### Changed - ⬆️ **Minecraft 26.3** for all platforms: Paper `26.3.build.178`, Fabric (Loader `0.19.5`, API `0.162.0+26.3`) and NeoForge `26.3.0.76` — all on Java 25. - 🧵 Fabric moved from Yarn to Mojang mappings (Loom `1.18`, Gradle `9.7.1`); NeoForge moved to ModDevGradle. - 🗂️ The 1.21.x builds live on in the `1.21.x` branch. ### Fixed - 🐛 NeoForge whitelisted players with a random UUID, so they couldn't join and `!remove` did nothing. - 🐛 NeoForge JAR didn't bundle JDA — now included via Jar-in-Jar. - 🐛 Fabric always reacted ✅, even if the name didn't exist. - 🐛 Removed users stayed in `whitelist-data.yml` after their last player was removed (Paper). - 🔒 NeoForge config is no longer a synced config, so the bot token is never sent to clients.

### Added - 📱 **Bedrock support (Geyser + Floodgate)** — prefix a gamertag with `.` (configurable via `bedrock.prefix`) to whitelist Bedrock players, e.g. `.Steve` or `.Cool Guy`. - 🔎 Gamertags are resolved to their Floodgate UUID through the GeyserMC Global API — no Floodgate dependency needed. - 🕒 Bedrock players unknown to the API are reserved and whitelisted automatically on their first join. - 🧩 Floodgate is detected (optional) and its `username-prefix` is checked against the configured prefix. ### Changed - ⬆️ **Minecraft 26.3** for all platforms: Paper `26.3.build.178`, Fabric (Loader `0.19.5`, API `0.162.0+26.3`) and NeoForge `26.3.0.76` — all on Java 25. - 🧵 Fabric moved from Yarn to Mojang mappings (Loom `1.18`, Gradle `9.7.1`); NeoForge moved to ModDevGradle. - 🗂️ The 1.21.x builds live on in the `1.21.x` branch. ### Fixed - 🐛 NeoForge whitelisted players with a random UUID, so they couldn't join and `!remove` did nothing. - 🐛 NeoForge JAR didn't bundle JDA — now included via Jar-in-Jar. - 🐛 Fabric always reacted ✅, even if the name didn't exist. - 🐛 Removed users stayed in `whitelist-data.yml` after their last player was removed (Paper). - 🔒 NeoForge config is no longer a synced config, so the bot token is never sent to clients.

### Added - 📱 **Bedrock support (Geyser + Floodgate)** — prefix a gamertag with `.` (configurable via `bedrock.prefix`) to whitelist Bedrock players, e.g. `.Steve` or `.Cool Guy`. - 🔎 Gamertags are resolved to their Floodgate UUID through the GeyserMC Global API — no Floodgate dependency needed. - 🕒 Bedrock players unknown to the API are reserved and whitelisted automatically on their first join. - 🧩 Floodgate is detected (optional) and its `username-prefix` is checked against the configured prefix. ### Changed - ⬆️ **Minecraft 26.3** for all platforms: Paper `26.3.build.178`, Fabric (Loader `0.19.5`, API `0.162.0+26.3`) and NeoForge `26.3.0.76` — all on Java 25. - 🧵 Fabric moved from Yarn to Mojang mappings (Loom `1.18`, Gradle `9.7.1`); NeoForge moved to ModDevGradle. - 🗂️ The 1.21.x builds live on in the `1.21.x` branch. ### Fixed - 🐛 NeoForge whitelisted players with a random UUID, so they couldn't join and `!remove` did nothing. - 🐛 NeoForge JAR didn't bundle JDA — now included via Jar-in-Jar. - 🐛 Fabric always reacted ✅, even if the name didn't exist. - 🐛 Removed users stayed in `whitelist-data.yml` after their last player was removed (Paper). - 🔒 NeoForge config is no longer a synced config, so the bot token is never sent to clients.

### Added - 📱 **Bedrock support (Geyser + Floodgate)** — prefix a gamertag with `.` (configurable via `bedrock.prefix`) to whitelist Bedrock players, e.g. `.Steve` or `.Cool Guy`. - 🔎 Gamertags are resolved to their Floodgate UUID through the GeyserMC Global API — no Floodgate dependency needed. - 🕒 Bedrock players unknown to the API are reserved and whitelisted automatically on their first join. - 🧩 Floodgate is detected (optional) and its `username-prefix` is checked against the configured prefix. ### Changed - ⬆️ **Minecraft 26.3** for all platforms: Paper `26.3.build.178`, Fabric (Loader `0.19.5`, API `0.162.0+26.3`) and NeoForge `26.3.0.76` — all on Java 25. - 🧵 Fabric moved from Yarn to Mojang mappings (Loom `1.18`, Gradle `9.7.1`); NeoForge moved to ModDevGradle. - 🗂️ The 1.21.x builds live on in the `1.21.x` branch. ### Fixed - 🐛 NeoForge whitelisted players with a random UUID, so they couldn't join and `!remove` did nothing. - 🐛 NeoForge JAR didn't bundle JDA — now included via Jar-in-Jar. - 🐛 Fabric always reacted ✅, even if the name didn't exist. - 🐛 Removed users stayed in `whitelist-data.yml` after their last player was removed (Paper). - 🔒 NeoForge config is no longer a synced config, so the bot token is never sent to clients.

### Added - 📱 **Bedrock support (Geyser + Floodgate)** — prefix a gamertag with `.` (configurable via `bedrock.prefix`) to whitelist Bedrock players, e.g. `.Steve` or `.Cool Guy`. - 🔎 Gamertags are resolved to their Floodgate UUID through the GeyserMC Global API — no Floodgate dependency needed. - 🕒 Bedrock players unknown to the API are reserved and whitelisted automatically on their first join. - 🧩 Floodgate is detected (optional) and its `username-prefix` is checked against the configured prefix. ### Changed - ⬆️ **Minecraft 26.3** for all platforms: Paper `26.3.build.178`, Fabric (Loader `0.19.5`, API `0.162.0+26.3`) and NeoForge `26.3.0.76` — all on Java 25. - 🧵 Fabric moved from Yarn to Mojang mappings (Loom `1.18`, Gradle `9.7.1`); NeoForge moved to ModDevGradle. - 🗂️ The 1.21.x builds live on in the `1.21.x` branch. ### Fixed - 🐛 NeoForge whitelisted players with a random UUID, so they couldn't join and `!remove` did nothing. - 🐛 NeoForge JAR didn't bundle JDA — now included via Jar-in-Jar. - 🐛 Fabric always reacted ✅, even if the name didn't exist. - 🐛 Removed users stayed in `whitelist-data.yml` after their last player was removed (Paper). - 🔒 NeoForge config is no longer a synced config, so the bot token is never sent to clients.

### Added - 📱 **Bedrock support (Geyser + Floodgate)** — prefix a gamertag with `.` (configurable via `bedrock.prefix`) to whitelist Bedrock players, e.g. `.Steve` or `.Cool Guy`. - 🔎 Gamertags are resolved to their Floodgate UUID through the GeyserMC Global API — no Floodgate dependency needed. - 🕒 Bedrock players unknown to the API are reserved and whitelisted automatically on their first join. - 🧩 Floodgate is detected (optional) and its `username-prefix` is checked against the configured prefix. ### Changed - ⬆️ **Minecraft 26.3** for all platforms: Paper `26.3.build.178`, Fabric (Loader `0.19.5`, API `0.162.0+26.3`) and NeoForge `26.3.0.76` — all on Java 25. - 🧵 Fabric moved from Yarn to Mojang mappings (Loom `1.18`, Gradle `9.7.1`); NeoForge moved to ModDevGradle. - 🗂️ The 1.21.x builds live on in the `1.21.x` branch. ### Fixed - 🐛 NeoForge whitelisted players with a random UUID, so they couldn't join and `!remove` did nothing. - 🐛 NeoForge JAR didn't bundle JDA — now included via Jar-in-Jar. - 🐛 Fabric always reacted ✅, even if the name didn't exist. - 🐛 Removed users stayed in `whitelist-data.yml` after their last player was removed (Paper). - 🔒 NeoForge config is no longer a synced config, so the bot token is never sent to clients.

### 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.

[1.0.0] - 2025-11-10 🎉 Initial Release ✨ Features - Discord Integration: Full Discord bot integration using JDA 5.0.0-beta.24 - Automatic Whitelisting: Add players to whitelist by simply typing their name in a designated Discord channel - Emoji Reactions: Clean feedback with emoji reactions (✅ for success, ⛔ for errors) - User Whitelist Limit: Configurable maximum number of whitelists per Discord user (default: 3) - Commands: - !list - View all your whitelisted players - !remove <player> - Remove a player from your whitelist - /whitelister reload - In-game command to reload configuration - Persistent Data Storage: Whitelist data saved to whitelist-data.yml and persists across restarts - Player Name Validation: Validates Minecraft usernames (alphanumeric + underscore, max 16 characters) - Configurable Settings: Customize bot token, channel ID, user limits, command prefix, and emojis 🔧 Technical - Minecraft Version: 1.21.1 (Paper/Spigot) - Java Version: 21+ - Lightweight Discord Bot: Uses JDA createLight() with minimal intents (GUILD_MESSAGES, MESSAGE_CONTENT) - Async Operations: All whitelist operations run asynchronously to prevent blocking - Singleton Pattern: Clean plugin architecture with centralized instance management