From f2c9d42f2fc01460604956a7ec7cf26dd20f5de8 Mon Sep 17 00:00:00 2001 From: Wendelin <32160662+Qendolin@users.noreply.github.com> Date: Sun, 27 Sep 2026 18:03:18 +0200 Subject: [PATCH 1/3] Revise binary search text for mod troubleshooting Updated the binary search guide for mod troubleshooting to clarify steps and emphasize backing up worlds. --- tags/guide/binarysearch.ytag | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/tags/guide/binarysearch.ytag b/tags/guide/binarysearch.ytag index c36b68aa..39f7a8c3 100644 --- a/tags/guide/binarysearch.ytag +++ b/tags/guide/binarysearch.ytag @@ -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 crash 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:** Keep core dependencies (like Fabric API) always enabled. Pick your suspect mods (or all mods if unsure). +2. **Split:** Divide your suspects into **Half A** and **Half B**. (Rough halves are fine.) +3. **Test:** Enable Half A. Disable Half B. Keep previously saved mods enabled. Launch the game. +4. **Check:** + * **Issue persists:** The bad mod is in Half A. Repeat from Step 2 using **Half A**. + * **Issue is gone:** Keep Half A enabled. Repeat from Step 2 using **Half B**. +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. From 586bf20908252bf6ef2cfac6848fa7f907855932 Mon Sep 17 00:00:00 2001 From: Wendelin <32160662+Qendolin@users.noreply.github.com> Date: Sun, 27 Sep 2026 18:04:59 +0200 Subject: [PATCH 2/3] Refine binary search troubleshooting steps --- tags/guide/binarysearch.ytag | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/tags/guide/binarysearch.ytag b/tags/guide/binarysearch.ytag index 39f7a8c3..c209c1a8 100644 --- a/tags/guide/binarysearch.ytag +++ b/tags/guide/binarysearch.ytag @@ -6,12 +6,12 @@ A **binary search** (aka **bisection**) quickly finds a broken mod without testi **Note:** Back up your world before testing, or use a temporary test world to avoid world corruption! -1. **Setup:** Keep core dependencies (like Fabric API) always enabled. Pick your suspect mods (or all mods if unsure). +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 previously saved mods enabled. Launch the game. +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**. - * **Issue is gone:** Keep Half A enabled. Repeat from Step 2 using **Half B**. + * **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. **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. From ecbbcb89fdcf3cb36c0a52e0c78cd8bddccdb8b8 Mon Sep 17 00:00:00 2001 From: Wendelin <32160662+Qendolin@users.noreply.github.com> Date: Sun, 27 Sep 2026 18:08:12 +0200 Subject: [PATCH 3/3] Change "crash logs" to "the logs" --- tags/guide/binarysearch.ytag | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tags/guide/binarysearch.ytag b/tags/guide/binarysearch.ytag index c209c1a8..5acd9a94 100644 --- a/tags/guide/binarysearch.ytag +++ b/tags/guide/binarysearch.ytag @@ -2,7 +2,7 @@ type: text --- -A **binary search** (aka **bisection**) quickly finds a broken mod without testing them one-by-one. Use this when crash logs don't give a conclusive answer. +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. **Note:** Back up your world before testing, or use a temporary test world to avoid world corruption!