This is a submission for the Hacktoberfest Open-Source AI Challenge Week 3: Slow and Steady

What I Built

Adding one Minecraft mod can turn a working pack into a wall of errors. I built Minecraft Ai Doctor to make that wall easier to understand.

Select a Prism, Lunar or Dawn profile, import a log, or paste console output. The app groups missing dependencies, duplicate mods and version conflicts, shows the original evidence, and explains what to check next.

It also looks up published mod releases and offers reviewed changes in a separate mod-only repair copy, with rollback. Your original instance stays untouched.

Demo

This is a native Windows app. The preview shows a synthetic version conflict and the steps it produces. You can reproduce it from the source:

cargo run --release --locked -- --log tests/fixtures/sodium-conflict.log

A video walkthrough has not been recorded yet.

Code

The source is MIT licensed:

Michaello2000 / Minecraft-Ai-Doctor

Minecraft Ai Doctor

Formerly Prism AI Doctor. Existing saved keys and local data continue to use the legacy storage identifiers; no credential or backup migration is required.

A native Rust desktop companion for Minecraft launch problems. Import a log or inspect a mod folder, get local findings with original file and line references, then optionally ask an open-weight model to explain the evidence.

Independent project. Not affiliated with Prism Launcher, Lunar Client, Google, Groq or Fabulously Optimized. MIT licensed. No launcher code is forked or bundled.

Before publishing a fork or source snapshot, follow the local publication checks. API keys belong in Credential Manager or your process environment, never in the repository.

Preview

The screenshot uses the included synthetic log, with no personal paths, logs or API keys. After building, open that example with cargo run --release --locked -- --log tests/fixtures/sodium-conflict.log. This is a desktop app; a recorded…

View on GitHub

How I Built It

The app uses Rust and egui. Local rules inspect bounded logs and mod metadata without executing JARs.

The optional AI layer has adapters for Google's hosted Gemma and Qwen through Groq. Cloud requests require a redacted preview and explicit consent. Repeated identical requests can reuse cached results.

AI citations must reference supplied evidence, and repairs use locally checked operations rather than model-generated commands.

The current build passes 42 automated tests. Provider adapters have been tested with mocked responses; live Gemma validation is still pending.

Why Does Open Innovation Matter?

I wanted the diagnosis rules and repair behavior to be inspectable. Anyone can read the source, contribute a rule or replace a provider adapter.

Open-weight models leave room for future self-hosting and adaptation. This MVP uses hosted APIs for AI; local inference is not implemented. The offline checks work without an API key.

The Lazy Payoff

I used real Prism and Lunar logs during development, including a Nvidium/Sodium conflict. The payoff is a clearer starting point instead of jumping between console output, mod folders and release pages.

I have not measured the time saved yet. Matching release metadata still needs testing in a disposable game instance.