strangely, "CONTROL Key Hold Down" and other commands based on my modified version of the <keyname> list still seem to work. It is only FORWARD that is no longer recognized and had to be changed to "Forward". I think this may have something to do with the Windows update I just installed, but I also remember having some sort of problem with this last night before that update was installed so I can't say for certain. Does anyone know why this is happening with only one word? It's like capitalizing this word is taboo to The Almighty Dragon or something...

"Don't argue with people who write with digital ink and pay by the kilowatt-hour." ~ Martin Golding

"Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code" ~ Dan Salomon

“Talk is cheap. Show me the code.” ~ Linus Torvalds

-Edgar
DPI 15.3, 64-bit Windows 10 Pro, OpenOffice & Office 365, Norton Security, Shure X2U XLR to USB mic adapter with Audio Technica DB135 vocal mic, Asus X299-Deluxe Prime, Intel Core i9-7940X (14 core, 4.3 GHz overclocked to 4.9 GHz), G.SKILL TridentZ Series 64GB (4 x 16GB) DDR4 3333 (PC4 26600) F4-3333C16Q-64GTZ, NVIDIA GIGABYTE GeForce GTX 1060 GV-N1060G1 GAMING-6GD REV 2.0 6GB graphics card with 3 1920x1080 monitors

I can't seem to reproduce the issue after rebooting my system, as the modified version of the keyname list no longer seems to be working on the original one works again. Absolutely no clue why it changed, but just to say to anyone's curiosity about what the difference between the lists was, the original list is this (for some reason the block quotes are not rendering on my browser. I checked the HTML and it's not working):

WINDOWS Key
CONTROL Key
SHIFT Key
ALT Key
FORWARD Key
UP Arrow
BACK Key
DOWN Arrow
LEFT Arrow
RIGHT Arrow
SPACE Key
SPACEBAR

the modified list is this:

WINDOWS Key
CONTROL Key
SHIFT Key
ALT Key
Forward Key
UP Arrow
BACK Key
DOWN Arrow
LEFT Arrow
RIGHT Arrow
SPACE Key
SPACEBAR

for some reason, recognizing the all-capped variant of one specific word (in this case "FORWARD") suddenly stopped working, but all other all-capped words stayed the same. It's a random enough change (especiallyconsidering it went back to "normal") to make me wonder if it has something to do with the voice model shifting, such that I could've possibly fixed it by training "FORWARD".

on a COMPLETELY separate note, why is there no way to reply with the advanced editor on this forum without replying to a specific post? I even tried messing with the URL to remove the PARENTID but, shockingly, ended up with a server error...

"Don't argue with people who write with digital ink and pay by the kilowatt-hour." ~ Martin Golding

"Sometimes it pays to stay in bed on Monday, rather than spending the rest of the week debugging Monday's code" ~ Dan Salomon

“Talk is cheap. Show me the code.” ~ Linus Torvalds