Hello, I want to kick players that are cheating, but the “You were kicked from this game:” part makes the kick message very ugly. Can you kick the player without the “You were kicked from this game:” part?
1 Like
No. Developer kicks must have that message prefixed as well as the assigned error code (267 iirc).
2 Likes
Maybe you could instead lag the Client to the point of a crash?
2 Likes
That’s a terrible idea to purposely try and crash the player.
4 Likes
I’d find it fine. If your anti cheat solution is 100% confident the client is cheating I’d bombard the client with as much garbage to crash it as possible. Prob would wait a certain amount of time to kick em in case it doesn’t work. No reason to be nice to a cheater’s CPU lol
4 Likes
Thanks for making me choke on my water. Had a hearty chuckle
2 Likes
I think my kind of garbage will be useless GUIs. But I am not sure if I can run a while true do loop for 1 client only
If you want your kick message to be spicy, you can add some newlines using \n. For example, if you want your message to look something like this,
You were kicked from this game:
cheater lol!
you would set the kick message as “\n\ncheater lol!”
You could always do a while true do statement to crash the player
while true do
end
Yeah but don’t do that. It’s a bad idea overall.
Client-side crashing is useless, especially to kick exploiters. Exploiters can stop any client-side kick/crash attempt. You have to kick using the server.
4 Likes
While an exploiter can stop anything run on the client, only some-what experienced ones will be able to find the script doing it. The premise of having a local crash is for a slight inconvenience to the unexperienced exploiter.
There is a verm script that makes an inf wait on a kick on client ultimately disabling it but for while true do you’d need to use Dex or Script Dumper to find the script so ;p
Regardless of the context, you shouldn’t do that on the client.
Exploiters do not need to be knowledgeable to do anything on the client. There are so many softwares such as Elysian, Synapse and other that allow for identifying local code, and abusing it in anyway how.
Exploiters can use ScriptContext:SetTimeout to time out any crashing attempts. So they don’t need to decompile anything.
2 Likes
i know it’s 2 years later but i think that there is a way, i found this game Dokomon - Roblox that seems to ignore the “You were kicked from this game:” prefix, i have yet to find out how
repeat until nil while true do end
well it doesn’t work so it is useless
Are you sure that isn’t a modified image or bug? The kick screen is handled by a CoreScript which appends the developer’s message passed from the Kick argument when constructing the modal. There isn’t a way to remove the message because the developer can’t interface with this in any way besides the Kick method.
I do not get the same result upon joining.
1 Like
Sadly no. But you can give a reason for the kick.
I have done it plenty of times for various reasons. I never found anything wrong with it.