When a menu stops working
How the library keeps one mod's broken menu from affecting the game or other mods' menus, what you see when it happens, and how to get it back.
On this page
The library keeps mods' menus apart: if one mod's menu breaks, only that menu turns off, and only until the game restarts. The game, the mod itself and every other menu keep working.
When one mod's menu breaks#
If a mod's menu runs into an error while it is being shown, the library:
- turns that mod's menu off for the rest of the session;
- writes the error to the game log once, naming the mod;
- leaves every other menu alone.
Afterwards:
- Opening that mod's menu shows a screen that says: This menu stopped after an error and is off until the game restarts. The game log has the details.
- In the Mod menus list, that mod's button is greyed out, with the same text as its tooltip.
- The mod itself keeps running. Only its menu is affected, so its features work and its settings stay as they were.
Restarting the game turns the menu back on. If the same error happens again, report it to that mod's author with the log (how to find the line).
When a button fails#
Not every error turns a menu off. If pressing a button or changing a setting fails, the error is logged and the menu stays open. The setting may not have changed; the menu often shows a message saying what went wrong.
When the library itself fails#
If the library can't hook into your game, for example because a new Minecraft version changed something it relies on, every mod menu turns off for the session and the error is logged once. The game and all mods still run; there are just no menu buttons. An update of the library fixes this.
What never happens#
The library doesn't crash the game. With no support for your exact Minecraft version, a broken menu or a failing hook, the result is always the same: some or all menus are missing, and the game keeps running.