I have not tested this on Windows or any other platform, so it’s possible this only occurs on macOS.
I’m on Mac. It’s been happening to me for the past day
I’m on Windows, not happening to me!
I am also on a Mac, and this does in fact happen in game, it’s very annoying
Yep, been happening on MacOS. Past couple days.
This is just an acknowledgment announcement!
We’ve filed a ticket into our internal database for this issue, and will come back as soon as we have updates!
Thanks for flagging!
Yeah, occurred to me too on mac
This is still actively occurring on my mac as well as many other people’s. Hope this can be resolved ASAP as it makes typing commands, chatting, and more very tedious.
Seems to be a mac keyboard issue, can someone with a mac keyboard on windows or vice versa test? it could either be mac keyboard or macos
It’s definitely not macOS here. As mentioned, I tested it in TextEdit and this started occurring even though I have not installed any system updates at the time.
Are there any updates to this? It’s been nearly a month and this makes using slash commands very frustrating
Hey, I got a fix in for this! You should see the change roll out in about a week or so
Mind looking into this issue?
Interesting username by the way
Edit: Oh, you updated it
I thought there was just something wrong with my keyboard! I’ve been having to delete the second slash every time.
This is just for Macs, though, my Chromebook does not have this issue (yes, you can get Roblox on Chromebook)
Not to be off-topic, just replying to your own reply’s topic which I think is okay?..
I have to agree.
Not to mention this is an old name… Meaning possibly his age was in his username.
Is there any Mac user not experiencing this issue? Also, does there exist a timeline for when the bug could be patched?
Wow—he must have a lot of experience after 2,013 years of life.
yea I am still experiencing this. very frustrating since I use /e for a game mechanic all the time
Any updates on the issue? Thanks
More like 3K days.
I’m not gonna go off-topic with this.
The issue is still persisting after 2 weeks. Do we have a different ETA of this fix?