.commands

[ataraxic]

When queuing for scenarios I was consistently missing the queue because I was stuck in combat. I asked in /advice what I should do and someone told me to type .u or .rvr in /say. I did that, but all that happened was my character said ".u" or ".rvr" out loud in /say. I also tried .rules to no avail.

I have since done the following things to troubleshoout:

1) disabled all addons
2) deleted addons folder
3) deleted game folder, redownloaded

None of the above have worked, including re-downloading the file from the .torrent. Has anyone had a similar issue? I would love to be able to continue playing here.

edit: I should also add that this issue is not character specific, but persistent through each of my characters.

[Acidic]

The standard fix that seems to work for in combat is
/say .u

[Natherul]

I have head that . commands would not work in one single case before, we could not establish why it happened however and since its so few occurrences its a hard job to find similarities and issues that would cause this problem.

[sullemunk]

Wounder if it has to do with keyboard configuration. If it sends a different .dot character code

[Hargrim]

Wounder if it has to do with keyboard configuration. If it sends a different .dot character code

Yeah, maybe try to change windows system keyboard language to English (US)

[Acidic]

Could be worth trying alt codes to get the dot
Alt 7 I think (long time since used them)

[Foomy44]

I heard someone complain about this in general chat once and the fix for him was a language setting somewhere, think it was an ingame one but not 100%.

[Natherul]

I heard someone complain about this in general chat once and the fix for him was a language setting somewhere, think it was an ingame one but not 100%.

Try if its solved by changing keyboard layout in windows. Its hidden a bit differently depending on your version of windows. Change it to en US just for testing

[sullemunk]

Also try a /lang 1

[ataraxic]

Thanks for all of the advice so far. Last night I created a new account and have been able to use commands successfully on that new account - which means that the issue is related to the actual account itself and not the game client. I will try some more trouble shooting with the bugged account today to see if we can isolate a reason for this error to be occurring.