TheHoboKingdom Search
Guides/Minecraft/Common fixes

Troubleshooting record

Change one thing at a time.

Keep the original profile intact, start with the smallest reversible test, and write down the change that actually fixes the problem.

Safe checksDiagnosis required

Inventory clicks and hotbar keys behaving strangely

This covers the symptom where clicking an inventory item immediately moves it to another slot while the number keys no longer select the hotbar normally.

  1. Tap and release Shift, Ctrl, and Alt once. A stuck modifier can make an ordinary click behave like a transfer shortcut.
  2. Open Controls and search the bindings used by the inventory-management, sorting, mouse-tweaks, or hotbar mods in the pack. Red conflicts deserve attention first.
  3. Check whether the number keys fail while walking in the world or only while an inventory is open. Failure everywhere points toward the hotbar bindings; inventory-only behaviour points toward an inventory mode or shortcut.
  4. Open the relevant client's mod settings and look for a transfer, sorting, lock, or alternate mouse mode that may have been toggled.
  5. Restart the client before changing files. If the behaviour remains, copy the profile and disable only the most likely client-side inventory mod in the copy.

Do not begin by deleting the whole configuration folder. That removes the information needed to identify which setting changed and can erase unrelated keybinds that were working properly.

Missing dependencies

  1. Read the first missing-mod or minimum-version line in the loader message.
  2. Confirm that the dependency matches the exact Minecraft version and mod loader.
  3. Install one required dependency at a time and launch again.
  4. Record automatic dependencies in the versioned manifest so the next player does not repeat the same search.

Crashes after adding or updating a mod

  1. Preserve the last profile that launched successfully.
  2. Read the crash report for the first named mod, mixin, missing class, or dependency rather than the final generic exit code.
  3. Reproduce the crash in a copied profile with the same world removed from the test.
  4. Undo the most recent change. If the copied profile launches, restore changes one at a time until the fault returns.
  5. Never open an important world with a mod set you know is incomplete unless its backup has already been checked.

One player cannot join

  • Compare the exported profile or manifest rather than relying on mod counts alone.
  • Confirm game version, loader version, mod versions, configuration files, and any world-required datapacks.
  • Separate network reachability from a mod mismatch: a timeout, rejected handshake, and missing registry entry are different problems.
  • Record the first successful joining method as the baseline before changing networking software again.