ModBisector is a tool for analyzing Minecraft mod collections and identifying hidden problems that are difficult to find manually.
It helps Minecraft modpack creators and players debug large modpacks by finding possible causes of crashes and startup failures.
Examples of problems ModBisector can help locate:
- Out of Memory crashes
- Broken mod files
- Invalid
mods.tomlfiles - Missing quotation marks (
") - Invalid line breaks in TOML files
- Other TOML parsing errors
Example:
com.electronwill.nightconfig.core.io.ParsingException:
Invalid newline in string. Are you missing a " quote?
Use \n to include a newline in the string.
Place ModBisector.bat into the Minecraft mods folder and run it.
ModBisector begins the testing process.
ModBisector divides the installed mods into two groups.
Example:
All Mods
├── Group A
└── Group B
Only one group is enabled while the other group is temporarily disabled.
The User Starts Minecraft with the selected group.
The user checks if the game works:
S = It starts successfully
C = It crashes
The result is given back to ModBisector.
If the selected group works, ModBisector saves it as a working group.
If the group crashes, the problem is somewhere inside that group.
The problematic group is split again:
Problem Group
├── Part A
└── Part B
The process continues until ModBisector finds the smallest possible group containing the problematic mod.
ModBisector uses a binary search approach.
Instead of testing every mod individually:
- 500 mods require around 9 tests
- 1000 mods require around 10 tests
This makes finding broken mods much faster.
ModBisector helps users find hidden Minecraft mod problems in large modpacks without manually removing and testing hundreds of mods.