Pressing M and getting nothing is the single most common Litematica complaint — and it is almost never the mod being broken. The main menu opens with the M key by default, and that key is contested territory: other mods claim it, keyboard layouts move it, and system software can swallow it. Work through the four causes below in order; the last section shows how to rebind the key once you can open the config, and how to get into the config when the menu key itself is the problem.
Cause 1: You Are on an AZERTY Keyboard — Press the Comma Key
Litematica’s hotkeys are defined by key position, and on AZERTY layouts the key in the M position is the comma key. The official documentation states it directly: on AZERTY keyboards, M becomes ,. So if your layout is French AZERTY or similar, press the comma key — the menu should open immediately. The same applies to the combination keys (M + C for the config GUI becomes comma + C, and so on). No settings need changing; the mod is already listening to the key you physically have.
Cause 2: Another Mod Owns the M Key
Minimap and waypoint mods commonly bind M (a full-screen map on M is a popular default), and various utility mods use it too. When two mods listen to the same key, one of them typically wins and the other appears dead — or the other mod’s screen opens instead, which at least tells you who took the key. You have two options:
- Rebind the other mod’s key in its own settings or in Minecraft’s Controls screen, if you want M to stay Litematica’s.
- Rebind Litematica’s menu key (next section) to something unused — many players put it on a key like
Nor a numpad key that nothing else claims.
The full default set — M main menu, M + C config, M + V Schematic Verifier, M + P Placements, M + G toggle schematic rendering, M + R toggle all rendering — is listed in our keybinds and hotkeys guide, which also explains how Litematica’s combination keys work.
Cause 3: System and Keyboard Software Is Eating the Key
Before blaming mods, rule out the layer underneath the game. Keyboard vendor software with macro profiles can remap or intercept keys per application; overlay and recording tools sometimes reserve keys; and if you play in a window, the operating system may treat the keypress as its own shortcut in some layouts. Quick test: does M type normally in chat and in other programs while the game runs? If the key is dead everywhere in-game but fine on the desktop, it points back to a mod or game-level binding (Causes 1–2). If it misbehaves outside the game too, fix the keyboard profile first. Also confirm you are in the game world and not sitting in a menu or text field where keystrokes go somewhere else — chat input, signs and search boxes all capture typing, including your M.
How to Rebind the Menu Key in Litematica
Litematica’s hotkeys live in its own config GUI, opened with M + C — which is awkward when M is the broken key. Two ways in:
- Use the layout key that works. If AZERTY is your case, comma + C opens the config directly.
- Free the M key first. Temporarily rebind or disable the conflicting mod’s M binding (Cause 2), press M to open the Litematica menu, and from there open the config GUI. In the config’s hotkeys section, set Litematica’s main menu (and any other combinations you use) to keys nothing else owns, then restore the other mod’s binding if you still want it.
While you are in the config, it is worth checking the related toggles: if the menu opens but the schematic never renders, M + G and M + R may be off — that symptom is covered in schematics not showing up.
A 60-Second Test Sequence
In a world, in this order: press the comma key (rules AZERTY in or out); open chat and type the letter M (proves the keyboard itself sends it); note whether something else opens on M (names the mod that took the key); then try M + C for the config. Whichever step behaves unexpectedly points at your cause in the sections above — and if none of the Litematica keys respond at all, treat it as a mod-not-loaded problem instead of a key problem.
When It Is Not the Key at All
If no Litematica key does anything and the mod is also missing from the mod list, the mod never loaded — a keybind guide cannot help, because there is nothing listening for the key. Go back to basics with Litematica not working: right mods folder for your instance, Fabric profile launched, one matched Litematica + MaLiLib pair. If the game instead shows a loader error naming malilib, that is the version mismatch case. Everything is indexed on the troubleshooting hub.
Frequently Asked Questions
Why doesn’t the M key open the Litematica menu?
Usually the key is taken or moved: another mod (minimap and waypoint mods commonly use M) claims it, or your keyboard layout differs. On AZERTY keyboards, the menu key is the comma key instead of M.
How do I change Litematica’s menu key?
Open the config GUI (M + C, or comma + C on AZERTY) and change the hotkeys there. If M itself is blocked by another mod, first rebind that mod’s key or free M temporarily so you can get into the config.
No Litematica key works at all. What does that mean?
The mod probably never loaded — check that it appears in the mod list, that you launched a Fabric profile, and that the matched Litematica + MaLiLib pair is in the mods folder of the instance you launched.
Next Steps
Keep the keybinds reference nearby while you play, and see how to use Litematica for the menu-driven workflow end to end.