/slashchat not working quite right...

As of yesterday, the default semicolon keybind hasn't been working right.

When you hit semicolon, it has always before started a chat command line with a semicolon. (For those who don't know, semicolon is a shortcut for /e, so ;salute, for example, is exactly the same as /e salute.)

Anyway, as of yesterday morning's patch, when I hit the semicolon key now, I get a command line that starts with a forward slash.

I'm used to quickly typing, for example, ";yes" to do the thumbs-up emote. Now, though, when I type that, I end up with "/yes" on the command line, followed of course by an error that yes isn't a valid command.

They're both mapped to the same keybind, which is "show chat$$slashchat". I'm guess that before, there was some mechanism to detect that the semi-colon key versus the slash key was being pressed, but maybe it was broken to correct the issue with all chat binds echoing the keystroke on the chat command line?

At any rate, it's not a big deal for me, I'll probably just change the keybind to "show chat$$beginchat ;", but I thought I'd post it here because you might want to consider changing the default keybind for it.

---

We've been saving Paragon City for eight and a half years. It's time to do it one more time.
(If you love this game as much as I do, please read that post.)

In the Keymapping Window, the command for "Start Chat (Include Keypress)" has been set to forward slash and semicolon. However, both open up chat with a forward slash. And even if I change the keys to any other key, it still opens with a forward slash.

So, yeah, they broke the command "Start Chat Include Keypress" by replacing it with /slashchat.

---

Speeding Through New DA Repeatables || Spreadsheet o' Enhancements || Zombie Skins: better skins for these forums || Guide to Guides

[ QUOTE ]
In the Keymapping Window, the command for "Start Chat (Include Keypress)" has been set to forward slash and semicolon. However, both open up chat with a forward slash. And even if I change the keys to any other key, it still opens with a forward slash.

So, yeah, they broke the command "Start Chat Include Keypress" by replacing it with /slashchat.

[/ QUOTE ]

I always thought "Start Chat (Include Keypress)" and /slashchat where the same thing.

My OLD bindfile (saved after i12) shows that slashchat has always been the bind for both:
/ "show chat$$slashchat"
; "show chat$$slashchat"

I always wondered why it ever showed a semi-colon to begin with... unless "slashchat" was simply the command to include the keypress. I guess we could have tested it by doing "bind M slashchat" and seeing if an M showed up, but I don't think anybody had a use for that type of thing.. and now that it doesn't work that way.. we can't even find out. lol

Maybe it got borked somehow when they "fixed" the "bound key shows up in chat" bug?

I say "fixed" because even though it doesn't do that every time now, there still seems to be a chance of your keystrokes being saved. Even though it didn't show up in the box as I was typing, I had my sent chat look like this:
"wwddddd awwh"
"ow's it goin?omg stupid bugs"

It was supposed to be:
"how's it going?"
"omg stupid bugs"

My first message was saved and displayed when I sent my second message. It's quite creepy, and it's happened a couple times so far. lol

---