Tags
Creators
Details
Licensed ARR
Published 3 months ago
Updated 3 weeks ago
All versions
0.6.5
Beta
Solver 0.6.53 months ago 14
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.x
1.20.x
1.19.x
1.18.x
Platforms
Bukkit
Folia
Paper
Purpur
Spigot
Changes
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 helpand 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).
Full technical changelog
- 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) orindividual(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 testused 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 reloadcommand to apply config changes without restarting the server. /solver helpand 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.
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:b96u2ZZt:sw0mOfIk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:b96u2ZZt:sw0mOfIk"
}

