Log/Crash Report analysis
Fealtous opened this issue ยท 3 comments
Hey, I'm sure you recognize me from forge in #player-support. I spend a lot of time in there so I've been able to mentally create a ton of shortcuts when figuring out why a crash occurred. I can explain to someone how I come to determine why something is broken, but often times it's a knowledge check.
For example, despite my request to resolve it, Choice Theorem's Overhauled Villages (CTOV) marks Lithostitched as a SERVER dependency when it should be BOTH. CTOV works fine when alone, but as soon as other mods are in the picture, worlds will fail to load until Lithostitched is added (barring any other issues of course). As a result, whenever registry errors are a part of the log, I immediately ctrl-f for CTOV and then for Lithostiched.
Another example would be Minecraft Dungeons Weapons inherent incompatibility with Forge because of their player reach mixin.
There are tons of other ones, but the suggestion is...
Do you have any interest in creating a resolution system? On a crash, perhaps check the modids for known problem causers and what potential resolutions might be. Or in the case of duplicate mods, suggesting to delete some. Obviously it would require some kind of repository of issues, but it may be worth it to reduce load on support.
If this is out of scope, totally understand.
Integration with Codex logs analyser is planned.
After it I can think about implementing what they don't want to implement(like hs_err).
Oh that's great to know there's already a project for that! I'll have to look into it when I've got some free time.