(Well, that's a mouth full)

For this issue, you will need a keyboard that has a 3-character key that expects another key press afterwards. If you don't have one available, please see the attached image and skip to the example in instruction 3.

INSTRUCTIONS:

1. Bind the key for opening the chat (with or without the '/' pre-added) to a 3-character key with an AltGr functionality which expects another keypress. For example, see the image and notice the button with the symbols "+ = ~". Set it to that if possible.

2. Press AltGr + <The binded key that you just set>.

3. Note: The chat will open with or not with a slash and everything seems normal, untill you press any key. It will type the symbol created by using the AltGr-function of the binded key. For example: (note the image), we bind the "+ = ~"-key to the "OPEN-CHAT"-function, then we press AltGr + "+ = ~"-key. It will open the chat for us, but when we type a diffrent symbol (like 'H') it will type '~H' in the chat.

It is quiete a small minor bug that isn't really important at all since not a lot of people will be pressing AltGr and a 3-function key at the same time.

I also want to note that the AltGr functionality of a key can also be triggered by pressing Ctrl and Alt at the same time. AltGr is essentially just a shortcut for it. This also means that the bug also appears when pressing Ctrl + Alt instead of AltGr with a 3-character key.

With 'a 3-character key that expects another key press afterwards', I mean a key like '+ = ~'. When pressed with AltGr or Ctrl + Alt, it will try to type the tilda, but before it does, it waits for another key input. When another key is pressed, it will try to combine the two. This will result in 'ã' being made if that key was 'a' or 'tilda f' if that key was 'f'. A key like '* $ ]' doesn't make the bug appear, because no other key input is expected.

I hope you kind of understood what I just said. Have a great day!