ВЕРСИИ (19)

## v1.10.0 — Discord notifications ### ✨ New: optional Discord notifications Detections can now be mirrored to a Discord channel, routed through **[DiscordSRV](https://modrinth.com/plugin/discordsrv)**. **Off by default, and nothing is bundled.** The jar still contains only this plugin's own classes — no shaded HTTP client, no JDA, no extra megabytes. The one class that talks to DiscordSRV is loaded only when you enable the feature *and* DiscordSRV is installed, exactly like the existing PacketEvents and sign-detection bridges. On a server without DiscordSRV, nothing changes at all. **Enable it:** ```yaml discord: enabled: true channel: "" # "" = DiscordSRV main channel | a game-channel name | a raw channel ID ``` Then /modblocker reload and /modblocker discord test. What gets posted — each can be switched off individually: ``` ┌───────────────────┬─────────────────────────────────────────────┐ │ Event │ Fires when │ ├───────────────────┼─────────────────────────────────────────────┤ │ channel-detection │ A forbiddenList plugin channel matched │ ├───────────────────┼─────────────────────────────────────────────┤ │ sign-detection │ A sign translation key came back translated │ ├───────────────────┼─────────────────────────────────────────────┤ │ escalation │ An escalation ladder rung was applied │ ├───────────────────┼─────────────────────────────────────────────┤ │ evade │ The sign check could never be completed │ └───────────────────┴─────────────────────────────────────────────┘ ``` One detection is one message. When the escalation ladder takes a detection over, it posts the escalation message and the per-detection one is skipped — you never get two posts for the same join. Detections with action IGNORE stay quiet unless you set include-ignored: true. Message text is templated in messages_<lang>.yml under discord:, so it follows your language: setting like everything else. Discord markdown works; Minecraft colour codes are stripped automatically. Nothing can ping by accident. With discord.mention empty, mentions are sent disabled — an @everyone that ended up inside a mod name or a kick reason renders as plain text instead of alerting your server. No performance cost. DiscordSRV's JDA owns the request queue, the rate limiting and the retries, so there is no queue or background thread in this plugin and every call returns immediately. A slow or unreachable Discord can never delay a player join. 🆕 New command /modblocker discord test — sends a test message through the real bridge and the real channel resolution, and tells you exactly why it did not go out (DiscordSRV still connecting / channel not found / DiscordSRV not installed). 📝 Docs The Java 21 requirement is now stated in the readme and the docs site, not just here on the plugin page. ⬆️ Upgrading Your existing config.yml is not overwritten, so it has no discord: section yet. A missing section simply means "off" — nothing breaks. To use the feature, copy the discord: block from the documentation into your config.yml and reload. Language files are unaffected: missing entries fall back to the copy bundled in the jar, so the new message templates work without you touching messages_*.yml. ⚙ Requirements Unchanged — FakeModBlocker is compiled using Java 21. Java 21 or newer is required to run this plugin.

▎Sign translation detection no longer overwrites whatever the player has on screen, and can no longer be skipped by keeping a menu open or never replying. ▎Heads-up: the check now waits for a busy screen, so it can start later than before. Set avoid-open-screens: false for the old behaviour. ▎Added an optional escalation system: the first join with a banned mod warns and kicks, the second one bans permanently. 

### Added - **Sign-translation: multi-key support.** `detect` now accepts a list of translation keys via `keys: [...]` in addition to the single `key`. Any one of the listed keys being resolved by the client is treated as a hit — useful for mods that ship several keybinds (Xaero, Litematica, JEI…) or where key names differ across mod versions. ```yaml MyMod: detect: keys: - "key.mymod.a" - "key.mymod.b" punishment: action: KICK reason: "..." The old key: "..." form still works — 100% config-compatible. Improved - Sign-translation support probe now tells you WHY it's disabled. Previously the console just said "current server/API does not support it"; now it names the exact class or method that's missing, e.g. ▎ Sign translation detection unavailable: missing method org.bukkit.entity.Player#openVirtualSign(Position, Side) (Paper API too old; sign-translation needs Player#openVirtualSign, which was added in Paper 1.21.5 and does not exist on 1.21.4 or earlier; Spigot and some Paper forks like Purpur/Pufferfish/Leaves may also lack it). - Makes it obvious whether you just need to update Paper, or whether you're on Spigot / a Paper fork that doesn't expose the sign API yet. Docs - config.yml now explains up-front that forbiddenList matches plugin-channel names, not mod display names, and points users to sign-translation.mods for client-only mods that never register a plugin channel. Multiple people were hitting this footgun. - Added a commented-out Xaero example showing multi-key config. Compatibility - No breaking changes. Existing configs continue to load untouched.

Fixed a misguiding debug message As always, with the latest version support

Fixed an issue about Paper forks

Fixed a rare false kick issue

·Added an optional PacketEvents support, which can improve the plugin channel detection performance. (It will be auto enabled when your server is using packetevents) ·Changed the default config file where it can detect the specified channel message

·Fixed the issue where an empty config will still detect mods ·Fixed the issue about reload command

·Added Minimessage support ·Fixed the issue when floodgate is installed in Velocity/BungeeCord

* Fixed a rare issue about sign detection (Note: we've been always supporting the latest server version ;)

Try to fix a rare issue that the sign detection won't auto-close

Fixed known floodgate support issue

try to fix floodgate support

try to fix floodgate support

try to fix floodgate support

* Just a notice that there's no need to wait for FakeModBlocker to add 26.1 support, because this little plugin might always support the latest server version ;) + Now You can select whether ignore bedrock players or not if you are using floodgate plugin to allow bedrock players to join. Therefore there's a new config added: ``` skip-bedrock-via-floodgate: true ``` So it might look like this: ``` extra-detections: sign-translation: enabled: true skip-bedrock-via-floodgate: true mods: Freecam: detect: key: "key.freecam.toggle" punishment: action: "KICK" reason: "&c&lWarning: Please do not use &b&lFreecam &c&lon this server." ```

* Fixed the issue that sign won't auto close

* Remade the new sign dectecting feature, now it no longer use the real oak_sign block in the world. * But I'm also afraid that this might also make the new feature also support 1.21.10+ Paper. Haven't tested yet.

# 🧩 FakeModBlocker A **lightweight**, **fully customizable**, and **cross-version friendly** mod detection plugin that monitors plugin channels to identify some mods like Xaero's World Map, Replay Mod, and known mod loaders such as **Fabric**, **Forge**, and more. It also supports an **optional advanced sign translation detection module** on supported server implementations. --- <img src="https://files.catbox.moe/8j2rr5.png" width="384" height="206" alt=""/> ## ✨ Features ✅ Lightweight — zero unnecessary overhead ✅ Fully customizable messages and behavior via `messages_xx.yml` ✅ Hex Color Code support for 1.16+ servers (e.g. `&#00ffcc`) ✅ No dependencies — drop-in and go ✅ Works across a wide range of server versions (1.8–1.21.11+) ✅ Multi-language support (`en`, `cn`, and your own language) ✅ Reload support: `/modblocker reload` ✅ Spigot / Paper / Purpur / Folia / PandaSpigot support ✅ Optional advanced **sign translation key detection** on supported server APIs --- ## 🔍 What it Detects FakeModBlocker primarily detects **clients or mods that register known plugin message channels**, such as: - `fml:hs` → Forge - `fabric:registry/sync` → Fabric - `xaeroworldmap` → Xaero's World Map - Any custom channel you define In addition, FakeModBlocker also provides an **optional sign translation detection module** for certain mods that expose identifiable translation keys. This advanced detection is configurable and can apply actions such as: - `NOTICE` - `KICK` - `BAN` - `IGNORE` --- ## 🧠 Detection Modes ### 1. Plugin Channel Detection This is the main detection method and works across the widest range of versions. It checks which `Plugin Message Channels` the player is listening on when they join. Many mod clients (e.g. Fabric / Forge and some utility mods) automatically register custom channels, which this plugin can detect and respond to. ### 2. Optional Sign Translation Detection This is an **extra optional detection module**. It works by opening a sign editor with specific translation keys and checking whether the client translates them, which may reveal the presence of certain mods. ⚠️ This feature depends on **server API support for opening sign editors**. If the current server version / implementation does not support the required public API, FakeModBlocker will **automatically disable this feature and skip it safely**. --- ## ⚠️ Important Notes ⚠️ **FakeModBlocker does NOT detect all mods or cheating tools.** It only works when the client exposes something detectable, such as known plugin message channels or supported translation-key behavior. ⚠️ This plugin should **NOT** be treated as a full anti-cheat or universal mod detector. ⚠️ The optional sign translation detection is an **additional enhancement**, not the main detection system. This makes FakeModBlocker ideal for detecting casual use of mod loaders or certain utility mods, but it should **not be treated as a complete anti-cheat / mod-blocking solution**. --- ## 📂 Installation 1. Drop the `.jar` into `plugins/` 2. Start the server to generate config files 3. Edit `config.yml` and your language file 4. Use `/modblocker reload` to apply changes instantly 5. Some mods are pre-configured in `config.yml`, and you can freely modify them to match your server rules --- ## ⚙️ Compatibility - Main plugin channel detection is designed to be broadly compatible with **1.8–1.21.11+** - Optional sign translation detection requires a compatible server API - On unsupported versions / server implementations, the sign detection module will be **disabled automatically** - Folia is supported through compatible scheduler handling --- ## ❓ FAQ ### Q: Can this detect hacked clients like Vape or LiquidBounce? **A:** No. Those clients often avoid using detectable plugin message channels. This plugin is best used to detect **mod loaders** like Fabric, Forge, Lunar, etc., and some configurable translation-key based mod detections on supported servers. ### Q: Is this an anti-cheat? **A:** No. This is a **mod presence detector**, not a cheat detection system. ### Q: How does it work? **A:** Its main method is checking which `Plugin Message Channels` the player is listening on when they join. Many mod clients automatically register custom channels, which this plugin can detect. Additionally, on supported server APIs, it can optionally use **sign translation key detection** for certain configurable mod signatures. ### Q: Does the sign detection work on every version? **A:** No. The sign detection module depends on public sign editor API support (Sorry i don't have much time to test every single version, but it should work on every Paper server i guess). If the server does not support it, FakeModBlocker will automatically skip that module without breaking the plugin.