2.3.0
ObserverLauncher 2.3.0
Better AI-assisted modpack building. If you use the MCP / AI integration to install mods, this release fixes the most common way a plan that "looks fine" ends up crashing your server on startup.
The big one: no more "looks fine, then crashes"
When an AI assistant installed a batch of mods for you, it could pick a version built for Forge on a NeoForge server, or for the wrong Minecraft version, and the plan still said everything was OK — then the server refused to start. That can't happen anymore:
- The planner now checks every mod against your real server (loader + Minecraft version) and refuses versions that don't match, instead of just warning.
- It works even for NeoForge/Forge servers that start from
run.bat(no.jarfile) — the launcher reads the server's own files to figure out what it is. - The batch installer skips any incompatible item and tells you which ones it skipped, and why.
Missing dependencies, caught before the crash
Some mods need other mods that aren't listed anywhere online — a classic example is Kotlin for Forge. The launcher now opens each downloaded mod and reads what it actually requires, then reports anything still missing before you start the server.
There's also a new check_mod_compat you (or your AI assistant) can run on any server: it scans mods/ for jars built for the wrong loader, client-only mods, missing required dependencies, and mods that are supposed to be absent (incompatible ones).
Better crash explanations
explain_crashnow reads the server log, not just the crash report. It used to say "No associated exception found" while the real cause — a missing mod, or a jar for the wrong loader — was sitting inlatest.log. It now lists the exact missing mods and skipped jars.- New
read_crash_reportreads a crash report directly from your server folder (the old file reader was rooted at the project, not the server).
Smaller improvements
- Searching the marketplace can now be pinned to a specific loader (NeoForge / Forge / Fabric / Quilt), so a NeoForge search no longer returns Forge builds. Searches also wait longer before timing out when several run at once.
list_contentnow shows each mod's loader and its client/server environment — so you can tell at a glance which mods are client-only (they do nothing useful on a dedicated server).check_performancesays "metrics are warming up" instead of showing an empty result right after a server starts.
What to watch out for
- These changes make the AI path stricter on purpose: if a mod genuinely has no build for your loader and Minecraft version, it will now be skipped rather than installed and crashing. You can still force a specific item through if you know what you're doing.
- Everything else — the setup wizard, Java handling, backups — is unchanged from 2.2.0.
Full technical changelog (for developers): see CHANGELOG.md → [2.3.0] in the repository.