Can a crash exploiter cause this error? (Same account launched from a different device)

Hey, me and @JakeyyDev are having a little argument about a crash exploit in our game.
We have been getting this errors in all servers with a difference of around 60 seconds between each server going down. this is happening every night for a few times.

Everyone in a server are getting this following error at the same time:

image

Could it be our fault in any way or is it Roblox’s?

4 Likes

It means you attempted to play a game on two devices at the same time on the same account. If this is an exploit I don’t know.

2 Likes

It happens to all of our players (~100) at the same time. no way 100 players can all login at a different device in the same time.

1 Like

This is strange because this message should only show when you have 2 instances of Roblox open or you are using your account on another device.

Often when an exploiter crashes this error will show since the first Roblox session is still open on their computer (frozen) and they will open another game instance.

If this message is showing to non-exploiters from your game then I recommend checking how much work the server is doing and ensuring no remote events can be spam fired to cause lag.

1 Like

is beacuse you playing on another device at the same time. try exit from the another device and you going to join to this game.

1 Like

In this case whole servers are experiencing the issue which is not normal.

1 Like

Correct me if I am wrong, but I am pretty sure RemoteEvents have a queue limit so this thing will not happen?

1 Like

I don’t think they do. I shouldn’t have done this but a while back I created a painting system that constantly fired remotes and I experienced no limit on how often I could fire it.

1 Like

It seems like they do exist (Img: ForeverHD @ Devforum)

2 Likes

image
Huh, can that give us some insight? maybe the Roblox chat system is not functioning properly?

EDIT: We have identified the exploiters as our competitors (:frowning:) and that can possible mean a lot. they would try everything to get rid of us

2 Likes

@GoldyyDev I would still strongly suggest reporting this once. Either on Bugs or Just in General for Hacking/Exploiting of your game by another group (Only If you are truly Sure). This error did happen with me twice and then it just goes away, it could be that this is an Internal Problem.

1 Like

you can make a script that every person in that group who entry in your game will get kicked

1 Like

This is an exploit, I would really like to shame these exploiters in public because it’s obvious that even if I will bring them on a plate to Roblox’s crappy moderation team, they would still not be banned.

It is an exploit in the old chat system that one of the builders accidently copied.

Check your chat to see if it is the latest

4 Likes

Well I think a Temporary Solution right now then is,
Making the Anti-Group Script, I would still strongly once again recommend bringing it in front of the Mod Team even if they do not do anything about it.

2 Likes

I put the new chat system and they can not exploit it.

This has become a rant about Roblox’s moderation team

2 Likes

Thanks for alerting everyone about this.

On the topic of Remotes. How old is the image you provided? If it’s recent then I imagine Remote Events reach a limit if multiple players are firing constantly.

1 Like

I noticed the problem has been solved but I still want to provide some relevant information!

This looks like it is caused by hanging the server. If the server is suspended it perhaps it can not tell ROBLOX that you have left the game.

Run down your code extensively to see if there is anyway someone could permanently take up the main thread; such as inserting a LOT of instances at once (causing the games engine to slow down significantly), or running code on the server; while true do end for example.

I often encounter this error because my ROBLOX did not close correctly and I fix it by opening task manager and closing the ROBLOX background process. You can open task manager on Windows by holding ctrl + shift + escape

You should be able to fix this error for everyone at once by force closing the server. You can force close a running server by going to the active places and clicking “Shut Down This Server” server on the 3 dot ribbon drop down.

1 Like

Trying to “shame” exploiters isn’t going to get anywhere. They live for negative reaction, and will continue making alts and new IPs if mods crack down on them.

I would be taking a look at your owns game code first before trying to put the blame on exploiters. People are always going to figure out how to mess with client-side stuff, which includes being able to fire RemoteEvents.

All games should be made with the assumption that a player out there is going to have full client-side power to run whatever they want, which is pretty much the case with exploits being accessible for the price of ~$20.

RemoteEvents must have some sort of cooldown if they are even using just a tad of processing power, and should have a if (player that doesnt need to use this) is firing then return end.

And for clarification, this isn’t a reply defending exploiters. I’m just saying that developers need to take the best of security practice into account because Roblox can’t carry everything

If you need help trying to put in anti-exploit measures, please feel free to message me :slight_smile:

2 Likes

is normal beacuse maybe he was playing on the roblox App from phone or maybe he was playing from his second Pc.

1 Like