ВЕРСИИ (12)

## Solver 0.10.2 <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/lE1D5PoR15w" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> **AntiVPN and integrity checks now run on your proxy — one check at the door for the whole network.** **Highlights** - **AntiVPN on the proxy** — put the same `Solver.jar` on BungeeCord, Waterfall, or Velocity and every connection is checked once, before it reaches any server. Same engine, same profiles, same calibration window, and FoxGate still always has the final word. - **Your proxy is verified too** — the proxy checks its own Solver jar against the official Modrinth release, scans the proxy's other plugins for known malware, and warns about Java agents. - **Every language, complete** — AntiVPN messages and `/solver help` are now fully translated in all 9 languages, and accents display correctly on older Windows servers. - **Updates no longer wipe your config comments** — new options arrive already documented, and on 1.8–1.17 they're applied without rewriting your `config.yml` at all. - **Sanctions, Staff Mode, and PlaceholderAPI are out of beta** — they've shipped since 0.7 and are now stable features. More details: [fyrx.net/en/solver/changelog](https://fyrx.net/en/solver/changelog)

## Solver 0.10.1 <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/GmJkSD4swwk" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> **Just a small update with bug fixes.** **Highlights** - **`/solver ban` and `/solver mute` take a duration** — `/solver ban Player 7d Griefing` is now a 7-day ban. - **Run Fyrx on a local model** — point Solver at Ollama, LM Studio, or any OpenAI-compatible endpoint, no API key needed. - **AntiVPN knows more VPN providers** — Proton, Surfshark, CyberGhost, Windscribe, PIA, TorGuard, Hide.me, and NordVPN's own networks are now caught. - **Clearer error alerts in-game** — staff now see the actual error (e.g. `NullPointerException: …`) instead of "check the console". More details: [fyrx.net/en/solver/changelog](https://fyrx.net/en/solver/changelog)

## Solver 0.10.0 <iframe width="560" height="315" src="https://www.youtube-nocookie.com/embed/GmJkSD4swwk" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" allowfullscreen></iframe> **New: AntiVPN — stop VPNs and proxies at the door, with a score you can actually read. Plus one jar for your whole network and Minecraft 26.x support.** **Highlights** - **New: AntiVPN** — blocks VPN and proxy connections out of the box, no API key needed. Known VPN networks are matched instantly, and a VPN provider's brand-new IP ranges are caught before any list catches up. - **Explainable, not a black box** — every detection gets a 0-100 score showing exactly why. No AI guessing, and nothing is enforced until Solver has calibrated on your own server. - **Plays nice with [FoxGate](https://modrinth.com/plugin/foxgate)** — if you run it, FoxGate always has the final word. Solver keeps alerting as an addon, or steps aside completely. - **One jar for your whole network** — drop the same `Solver.jar` on your BungeeCord, Waterfall, or Velocity proxy and staffchat + alerts reach staff on every server. - **Faster to type** — command aliases like `/v`, `/sc`, `/invsee`, and prefix-less commands (`/vanish`, `/inspect`) now actually work. - **Minecraft 26.1 – 26.3 supported**, alongside 1.8.8 – 1.21.x. *Privacy: AntiVPN's real-time lookups share a connecting player's IP with IPQuery.io and ipapi.is, and Solver now sends anonymous usage stats via bStats. Both can be turned off in `config.yml`.* More details: [https://fyrx.net/en/solver/changelog](https://fyrx.net/en/solver/changelog)

## Solver 0.9.1  **Solver now runs on plain Spigot/CraftBukkit, not just Paper/Folia — all the way back to 1.8.8.** **Highlights** - **New: Spigot/CraftBukkit support, 1.8.8 and up** — Solver no longer requires Paper. Every feature (chat moderation, sanctions, staff mode toolkit, GUIs) now works on plain Spigot too, with legacy-appropriate fallbacks where a Paper-only API doesn't exist (e.g. hiding a vanished player from the server list only works on Paper — there's no vanilla equivalent — but everything else works the same everywhere). - **Lowered Java requirement: Java 8 or higher** (was Java 17). - **Fixed:** sanctions storage (SQLite) could fail to initialize on some setups due to a driver registration issue specific to how Bukkit loads plugins. More details: [docs.jeamcube.com/en/solver/changelog](https://docs.jeamcube.com/en/solver/changelog)

## Solver 0.9.0  **Solver can now verify its own jar and scan for known-malware plugins.** Both static, signed, and cached — no dynamic backend involved yet. **FyrxLab Backend (Beta): Solver can now verify its own jar and scan for known-malware plugins.** Both static, signed, and cached — no dynamic backend involved yet. **Highlights** - **New: build integrity + malware scanning** — Solver verifies its own jar against a signed hash published by FyrxLab, and scans every other `.jar` in `plugins/` against a list of known-malware hashes. Both are static, signed files cached locally and refreshed only every so often, not a live backend. Check anytime with `/solver integrity`, or force an immediate check with `/solver integrity rescan`. - **Optional: Modrinth cross-check for unflagged plugins** — plugins that don't match the malware list can also be checked against Modrinth's public hash database, purely informational (never a red flag on its own — plenty of legitimate plugins simply aren't on Modrinth). - **New: Java agent detection** — Solver now warns at startup if a Java agent was attached to the server's JVM, since an agent can patch classes in memory (including this very integrity check) without ever touching the jar file on disk. - **Fixed:** `/solver rtp` could occasionally teleport the person running the command to themselves instead of another player. More details: [docs.jeamcube.com/en/solver/changelog](https://docs.jeamcube.com/en/solver/changelog)

## Solver 0.8.0  **Solver is now a full moderation/staff alternative** Alt-account tracking, MySQL support, in-game appeals, a full staff reports system, and a much deeper Staff Mode Toolkit — all backed by the same generative + algorithmic moderation engine. **[Docs are live](https://docs.jeamcube.com/en/solver/)** with everything below. **Highlights** - **Real alt-account detection, not just a name blacklist** — `/solver checkuser <player>` shows every account that ever shared an IP; a ban now instantly kicks an alt that's already online, not just future logins. - **In-game appeals + a full Staff Reports system** — `/solver appeal` and `/solver report`/`reports`, both with their own GUI, both notifying the right people automatically. - **A much deeper Staff Mode Toolkit** — named combined profiles, two-tier vanish, a private freeze chat channel, and `/solver inspect`/`enderchest` with click-to-confiscate. - **Optional MySQL storage** for multi-server setups, plus **CommandSpy** for a live relay of staff commands. - **Chat moderation categories are now yours to define** (`tags.yml`), and you can map any tag straight to a sanction type (`chat-moderation.action.tag-overrides`) - including the only way to reach an automatic ban from chat moderation. - **A real round of bugs found in our own pre-release testing, all fixed** - a config-wipe bug, false-positive chat flags on normal conversation, `/solver god` not stopping PvP, and a couple of missing staff/reporter notifications. More details: [docs.jeamcube.com/en/solver/changelog](https://docs.jeamcube.com/en/solver/changelog)

## Solver 0.7.2  **Chat moderation stops trusting a single AI call, staff commands get much faster to type, and the next milestone's toolkit ships early as experimental.** Multi-signal corroboration for sanctions, 4 configurable levels of how much the AI gets involved, standalone commands for staff/sanctions/moderation, and (experimental) vanish/freeze/staff-chat with granular per-command permissions. **Highlights** - **Experimental: Staff Mode Toolkit** — `/solver vanish`, `/solver freeze <player>`, and `/solver staffchat`, all under `/solver` and also available as standalone commands (see below). Early, in-progress piece of the next big milestone, shipped now instead of waiting on it — expect rough edges. - **Experimental: Granular permissions, LuckPerms-friendly** — every `/solver` subcommand now has its own permission node, grouped under `solver.diagnostics.*`, `solver.sanctions.*`, and `solver.staffmode.*`. `solver.admin` still grants everything, fully backward-compatible with existing OP-based setups. - **Staff/moderation commands no longer need the `/solver` prefix** — `/vanish`, `/mute`, `/ban`, `/moderation`, and more now work directly, with `/solver <command>` still working exactly as before. Toggle a whole category off in `config.yml` if another plugin already claims one of those names. - **Chat moderation no longer sanctions on the AI's word alone** — a real warn/mute/kick only fires automatically when the AI verdict is both very confident and severe, or when an independent local signal backs it up. Otherwise it stays a staff-only alert for manual review. - **4 configurable levels of how aggressively chat moderation calls the AI** — from never (local filter only, no AI provider needed) to real-time per-message. More details: [docs.jeamcube.com/en/solver/changelog](https://docs.jeamcube.com/en/solver/changelog)

## Solver 0.7.1  **Bug-fix patch** Five real bugs found via code audit right after 0.7.0 shipped, all fixed here. - Fixed: `config.yml` could lose its explanatory comments on every restart, even when nothing actually needed updating — it now only rewrites the file when a setting is genuinely missing. - Fixed: `/solver tempmute` with a duration under a minute (e.g. `30s`) silently did nothing — the mute expired before it ever took effect. Durations now apply with full precision. - Fixed: a rate-limit bug that could make Gemini-backed features (crash analysis, chat moderation) briefly block each other when sharing the same API key, instead of just waiting their own turn. - Fixed: a couple of internal Bukkit API calls in chat moderation and the sanctions commands were happening off the correct thread — hardened for Folia safety, and sanction commands no longer block on database I/O while running.

## Solver 0.7.0  **Sanctions, custom messages, and a better chat moderator.** This release brings a real warn/mute/kick/ban system, every player-facing message is now yours to customize, and Fyrx's moderation calls now come with a confidence score instead of a flat yes/no. **Highlights** - **New `messages.yml`** — every player/staff-facing message (help, errors, sanctions, moderation alerts) is now configurable with full MiniMessage support, in your own language folder (`lang/{locale}/messages.yml`). - **New Sanctions system (BETA)** — `/solver warn|mute|tempmute|kick|ban|tempban <player> [duration] <reason>`, plus `/solver unban|unmute|unwarn`, `/solver history <player>`, `/solver check <id>`, and `/solver note <player> <text>`. Every sanction gets a real ID, persists in `sanctions.db`, and shows its own correctly-worded message (a kick doesn't say "banned"). New and still under active testing. - **Bans are actually enforced now** — reconnecting while banned is rejected at login, not just a one-time kick. - **Mutes always work** — even with AI chat-moderation turned off, `/solver mute` now really blocks chat. - **New: Confidence Meter** — every moderation verdict now shows how *sure* Fyrx is that it's correct (0-100%), separate from how severe the behavior is. Visible in staff alerts, `/solver moderation test`, and averaged in `/solver moderation status`. - **`/solver moderation status` now shows a countdown** to the next automatic chat scan, so you're never left wondering if it's working or just waiting. - **New: PlaceholderAPI support (BETA)** — `%solver_muted%`, `%solver_warns%`, `%solver_active_sanctions%`, and more, for your scoreboard/tab-list/chat plugins. Optional, does nothing if you don't have PlaceholderAPI installed. - **`config.yml`/`messages.yml` no longer go stale on update** — new options added by a future update now merge in automatically instead of silently only working off an invisible default. - **AI Chat Moderation, out of beta** — staff/admins can now be exempted so they're never muted by their own system, full localization in all 9 languages, and a fixed bug where a single word ("harmless"/"toxic") replaced a real per-category, per-offender verdict. More details: [docs.jeamcube.com/en/solver/changelog](https://docs.jeamcube.com/en/solver/changelog)

## Solver 0.6.5 (Beta) **Beta feature this release:** AI Chat Moderation. It's off by default and still being tested — see below. ### Highlights - **New (Beta): AI Chat Moderation** — Fyrx can now watch chat and tell real harassment apart from friends just joking around, without a "banned words" list. Off by default (`chat-moderation.enabled: false`), still under testing. - **Fixed:** Solver no longer shuts itself down if you forget to set an API key — it now just warns you and keeps running. Fix your config and run `/solver reload`, no restart needed. - **New:** `/solver reload` — apply config changes on the fly, without restarting the server. - **Cleaner:** `/solver help` and error messages are properly formatted now. - **Stability:** Several stability fixes under the hood (a memory/thread leak, and the AI rate-limit is now shared correctly between features). <details> <summary>Full technical changelog</summary> - AI Chat Moderation (beta): reads a rolling window of recent chat and asks the AI for a verdict (harmless / toxic / harassment) with severity and reasoning — never a keyword blacklist. Configurable response: alert staff only, warn the player too, or auto mute/kick. Every flagged case is logged under `moderation-reports/`. - New `chat-moderation.scan-mode`: `bulk` (default, cheaper, one AI call per cycle) or `individual` (one check per active player, more accurate, costs more). - Fixed: chat moderation could miss serious messages that didn't match its internal trigger hints — it now checks every new chat activity, not just flagged ones. - Fixed: in auto-action mode, Fyrx could have punished the victim instead of the offender. Now fixed with separate offender/target fields. - Fixed: `/solver moderation test` used to print raw JSON — now shows a clean, colored summary. - No more self-disabling on a missing API key — Solver stays enabled and tells you what to fix. - New `/solver reload` command to apply config changes without restarting the server. - `/solver help` and unknown-command messages are now properly formatted instead of Bukkit's generic usage text. - Fixed a thread leak in the console error monitor. - Fixed a rate-limit bug that could let Solver's different AI features together exceed Gemini's real request limit. - The post-mortem crash-analysis prompt (written back in 0.5.0 but never actually used) is now wired in properly. - Several previously-ignored config options now actually work: `error-cooldown-minutes`, `analysis.timeout`, `analysis.save-to-file`, `notifications.notify-admins`, `notifications.send-to-chat`. </details>

### Solver 0.6.0 Changelog Version: 0.6.0 Compatible with Minecraft Paper/Purpur/Spigot 1.18+ === Updates: - Folia Support: Native detection of Folia servers. Fyrx now schedules all console output through the GlobalRegionScheduler on Folia instead of the classic Bukkit scheduler, and TickMonitor disables itself automatically on Folia (which already has its own watchdog). - New Command /solver analyze-last: Lets admins manually re-trigger a Fyrx analysis of the most recent crash-reports entry on demand, without waiting for a restart. - Smarter Console Error Batching: Console errors are now collected in a rolling buffer (up to 100 lines) and grouped into a 10-second batch window before being sent to the AI, with a 60-second global cooldown between analyses to avoid burning through the AI provider's rate limits. - TickMonitor Threshold Tuning: The freeze-detection threshold was raised from 5 to 15 seconds to reduce false positives from short, harmless lag spikes. Support: support@jeamcube.com Wiki English: Not ready yet (Sorry) Wiki Spanish: Not ready yet (Soon) Community: https://discord.gg/EdcYuBAdFB Best regards, the FyrxLab team.

### AbsoluteSolver 0.5.0 Changelog Version: 0.5.0 Compatible with Minecraft Paper/Purpur/Spigot 1.18+ === Updates: - Initial Public Release: First stable version of AbsoluteSolver. - Gemini AI Integration: Fully integrated with Google's gemini-3-flash-preview model to act as an AI-powered server administrator. - Live Console Monitoring: Injects directly into the server's Log4j engine to intercept ERROR and WARN exceptions the moment they happen. - Post-Mortem Crash Analysis: Automatically scans the crash-reports folder on startup and translates cryptic Minecraft crash logs into actionable solutions. - Native JVM Crash Support: Detects fatal Java crashes (hs_err_pid.log) and explains which native library or memory issue killed the server. - Early Startup Detection: Safely reads logs/latest.log upon booting to catch dependency or version errors that occurred before AbsoluteSolver even loaded. - TickMonitor (Lag Detection): A lightweight asynchronous thread that monitors server TPS. If the main thread hangs for more than 5 seconds, it generates a thread dump and identifies the exact plugin causing the deadlock. - Console UI Formatting: Features a custom ASCII startup banner and beautifully formats all AI responses using native Minecraft color codes directly in the console. - Diagnostic Tools: Includes the /absolutesolver crashme command so admins can safely test the AI's capabilities without breaking their server. - Asynchronous Architecture: 100% Asynchronous logic with zero impact on server TPS. Support: support@jeamcube.com Wiki English: Not ready yet (Sorry) Wiki Spanish: Not ready yet (Soon) Community: https://discord.gg/EdcYuBAdFB Best regards, the FyrxLab team.