Recently a game I’ve been working on has been crashed, the cause of it seems to be remote abuse, however that’s up in the air, what we do know is that when the game is being crashed the server spits out the following debug/error messages.
Players: :onRemoteSysStats disconnect Players: :onRemoteSysStats disconnect not in the client
Notice This is client inflicted, a specific user is crashing our games and has demonstrated to us numerous times that he is indeed the one doing it. He refuses to tell us how he’s doing it, he’d rather use it as a form of leverage.
Update User informed me that he can do this on almost all ROBLOX games, not sure if he’s bluffing but I felt like I should put it out there
Client inflicted or not, this is almost certainly out of your hands and you should file an engine bug for it.
Another thread had a similar output seen – without not in the clist. From that thread, Players::onRemoteSysStats seems to be related to a PlayerRejoining signal, does the player keep rejoining the server?
It doesn’t seem like it, another friend of mine had the same theory, I did checks to see if the player was rapidly rejoining, etc… ended up being a dead end.
@colbert2677 I saw that as well. Branching off of what @ankurbohra04 said, I feel like the player may be manipulating it to rejoin at a rapid rate, etc…
Write an engine bug report then. These kinds of support comments don’t get seen and they don’t exactly add new information to the thread either; they’re excess noise.
The error shouldn’t be a problem anymore. A few ROBLOX Staff Members contacted me to attempt and dissect the problem. Later telling me that they’ve fixed the issue (it was with the chat system)
Are you sure you’re not using an old forked version of the ROBLOX Chat?
