Recent content by Cassiopeia

/show is the only notable command where this occurs. Everything else that can't be broadcast or used in PMs carries a room specific function or something else of the like where it's intuitive. /show is specifically limited to prevent abuse.

Please do not claim suggestions until they are approved. This is a no because a) we are deprecating our use of Pokepaste as a third party tool and b) for abuse reasons. I’ll check on the rest with the relevant parties.

If you want to skip validation, just challenge people to the format ``Gen [num] Custom Game`. That has no validation whatsoever except for that which you place on it.

Since it's come up a couple of times, I may as well note this sums up accurately most of the issues with recruiting other users. With regards both to a reporting process in general and recruiting others to do it specifically, it should be noted that the access necessary to accurately verify a...

Chess.com can afford to act reactively to these problems and just remove people from ladders after the fact, whereas our system of usage stats as it stands right now cannot without in essence having to make things up after the fact. We'd have to throw out bot results entirely, which means...

Stepping in as the person who handles these matters of moderation and tech: This is not feasible to enforce by any means. Either we leave loopholes large enough to let many bots through, thus not solving the problem, or we close them tight enough that we block out innocent users, making things...

This is not punishable. The only punishment we'll give for this is already enforced by the simulator - a loss of ELO.

Seconding what hoeen said. Permalock is a punishment, your privileges were revoked for a reason. You have to earn them back. I'm certain it's annoying to have to walk people through challenging you, but that's the price of these things. Closing, have a nice day.

Going to move this to rejected upon assessment. There's no good way to do this without notable breaking protocol changes, which honestly aren't worth the trouble.

As it stands, this is unfortunately an intended interaction with how forms work on the server - they're intentionally meant to erase themselves per UX standards. Ideally, in the long term, we would render this page entirely on the client, but for the moment that's held up due to Preact. I'm...

We are not going to do this. The timer exists for people to use - to think, to go use the bathroom, to cope with bad internet, etc. Actual timerstalling is prevented by the mechanics of the timer - the rest of the time is theirs to use as they please.

I'm going to say no to this since CTRL-F exists for this purpose