Log Analyzer

Automatic analysis

When the game crashes:

1. Stuzhik opens the analyzer automatically
2. Shows the problems it found
3. Possible solutions for each one
4. Buttons for automatic fixes (where possible)

Manual analysis

If you need to run the analysis yourself:

1. Open the instance
2. The "Analyze Logs" button
3. Choose the log type:
   • crash-report - the latest crash
   • latest.log - the current session
   • Pick a file manually

Problem types

Critical

Block the launch completely:

Problem	Cause	Solution
Java version mismatch	Wrong Java version	Stuzhik installs the right one
Missing dependency	A required mod is missing	Automatic install
Mod conflict	Incompatible mods	Remove one of the mods

High

Cause a crash during play:

• OutOfMemoryError
• Mixin conflicts
• ClassNotFoundException
• NullPointerException in a mod

Medium

Can cause problems:

• Deprecated warnings
• Config errors
• Missing textures/models

Low

Don't affect the game:

• Info messages
• Debug logs
• Performance warnings

Solutions

Automatic

The "Apply" button for:

Removing a mod:

Remove problematic_mod.jar

Increasing memory:

Was: 2GB → Now: 4GB

Installing a dependency:

Install fabric-api-0.92.0.jar

Changing a config:

config/mod.toml: option = false → true

Manual

Step-by-step instructions:

1. Download mod X, version Y
2. Delete the old version
3. Put the new one in mods/
4. Restart

Live monitoring

Turning it on

1. Launch the instance
2. Stuzhik starts monitoring automatically
3. An indicator in the header shows the status

Events

Warning: Warnings from the log

[Sodium] Incompatible mixin detected

Error: Errors that don't crash the game

[KubeJS] Script error in startup.js:15

Crash: A full crash

Game crashed! Analyzing...

Notifications

When a problem is detected:

1. A pop-up notification
2. A list of problems in the live panel
3. Buttons to fix them

Knowledge base

Learning

When you apply a solution:

1. Stuzhik saves the result
2. "Helped" / "Didn't help"
3. The success rate is updated

Personalization

Solutions are ranked:

Solution	Success Rate	Shown
Remove mod	95%	✅ First
Update	70%	✅ Second
Change config	30%	⚠️ With a warning

Export

For a report

The analyzer's buttons after an analysis:

• "Export" — the analysis report as .json (you can open it again with the "Import" button)
• "Copy as Markdown" — the report to the clipboard, to paste into a chat or on GitHub

For support

When you contact a mod's author:

1. The "Archive" button (available for an instance) — saves a .zip
2. It includes:
   • latest.log and the end of debug.log
   • The latest crash reports (up to 5)
   • Stuzhik's analysis
   • The instance name
3. Attach it in Telegram (in Russian)

Error patterns

Stuzhik recognizes ~50 types of errors:

Java

• OutOfMemoryError
• StackOverflowError
• UnsupportedClassVersionError
• NoClassDefFoundError

Minecraft

• Missing registry entries
• Invalid block states
• Corrupted chunk data
• Missing textures

Mods

• Mixin conflicts
• ASM transformation failures
• Config parsing errors
• Dependency issues

Loaders

• Forge mod on Fabric
• Missing Fabric API
• Incompatible loader version