Is It Possible To Bind The # Key...

...on a german keyboard? This is a seperate key, it is not on Shift+3.

Starting with the obvious- did you try # and see what happens?

Edit: digging around found these charts but not sure the relevance:
https://community.bistudio.com/wiki/DIK_KeyCodes
DIK_BACKSLASH or key 43 appears to be the key in question.

bind # input /lockon
Invaild key provided.

bind DIK_BACKSLASH input /lockon
Invaild key provided.

bind \ input /lockon
Invaild key provided.

Can see valid bind keys here. # is not a valid bind key, it is modifier like shift or ctrl.

You need to find what key mapping is the key you want to bind from the key mapping list. Then use the text description, not the code map (DIK_XX) to bind it.

Maybe keyboard layout will show you the key code, idk. If the key you want to bind is not on the key mappings list you can't bind to it.

But you can use remapping software to change the german # key to something windower knows about, eg one of the special keys at the bottom, and use that.

Coming back to this, trying a bind on backslash seems to require an escape character:

bind \ input /lockon
Invalid key provided.
bind \\ input /lockon
Bound .

However, it doesnt bind anything. The key is listed in the valid bind keys. Is there a way to do this?

(Using this way, binding / is possible and working.)

Hello! For us yuropeen people, symbols on the keyboard are all out of whack. This is because of how windower receives the keypresses - basically for windower all keyboards are the en-US keyboard, no matter what system locale you actually have.

The workaround is to open the windower console, push the button you want to bind, and see what character is actually inputed in the console by that button. Then bind that character.

For example, on my it-IT keyboard, to the left of 1 and above the Tab key, there is the \ character, but on an en-US keyboard that location is where the ` character is. So if I want to bind my \ character, the command to use is bind %` somealias.

This is unfixable so we have to keep dealing with the workaround.

Hope this helps!