Skip to content

Revise binary search tag #236

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Shnupbups merged 3 commits into from
Oct 18, 2026
Merged

Revise binary search tag #236

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f2c9d42
Revise binary search text for mod troubleshooting
Qendolin Sep 27, 2026
586bf20
Refine binary search troubleshooting steps
Qendolin Sep 27, 2026
ecbbcb8
Change "crash logs" to "the logs"
Qendolin Sep 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions tags/guide/binarysearch.ytag
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,16 @@ type: text

---

A binary search can be used to quickly find a specific mod causing trouble, which can be especially useful when logs don't give a conclusive answer to your issue.
A **binary search** (aka **bisection**) quickly finds a broken mod without testing them one-by-one. Use this when the logs don't give a conclusive answer.

Start by removing or disabling half of your mods, then test if the problem still occurs. If it does, remove half of the remaining mods and test again. If it doesn't, add back half of the mods you just removed.
**Note:** Back up your world before testing, or use a temporary test world to avoid world corruption!

Keep in mind you don't have to stick strictly to halves each time, and may have to enable some library mods like Fabric API out of order.
1. **Setup:** Always keep core dependencies (like Fabric API) enabled. Start with all installed mods (or a specific group if you suspect them).
2. **Split:** Divide your suspects into **Half A** and **Half B**. (Rough halves are fine.)
3. **Test:** Enable Half A. Disable Half B. Keep any working mods from previous steps enabled. Launch the game.
4. **Check:**
* **Issue persists:** The bad mod is in Half A. Repeat from Step 2 using **Half A** as your new suspects.
* **Issue is gone:** Half A is safe! Keep Half A enabled, and repeat from Step 2 using **Half B** as your new suspects.
5. **Done:** Stop when only 1 suspect remains. That mod is the culprit.

By repeating this on an increasingly smaller set of mods, you'll find the problematic mod within a few iterations.
**Still having issues?** If you remove the culprit and the issue still persists, keep your working mods enabled and repeat from Step 1 to find the next bad mod.
Loading