Console bugs when bound to composable key

[mitchelvankleef]

Describe the bug
When the console key is bound to a composable key (for example ~ in some languages (e.g. Dutch)), it automatically closes when you start typing if the first character you are typing is not composable.

To Reproduce
Steps to reproduce the behavior:

1. Set your keyboard language to a language with composable keys (e.g. Dutch/NL);
2. Bind the console to a composable key (e.g. '~');
3. Open the console with this key;
4. Start typing, and make sure the first character is a letter that is not composable;
5. The console now closes.

Expected behavior
Console stays open and you can type as expected.

Version information (please complete the following information):

• OS: Windows 11 25H2
• OpenMoHAA Version: Medal of Honor: Breakthrough 2.41+0.83.0 (OpenMoHAA 0.83.0-dev+1095.b8a20d9) win_msvc64-x86_64 Feb 01 2026 UTC

[smallmodel]

The behavior is by design because the application depends on text input from low-level. When pressing ALT GR + dead key, the OS waits for another key press before sending ~ to the application.
~ must be removed from cl_consoleKeys as a workaround.

There is an upstream issue that was opened long ago on ioquake3 to improve the behavior ioquake/ioq3#285

In OPM the console can be opened using the top-left key (US is ~) or SHIFT+ESC.