“You were kicked from this game:Exploiting is a bannable offense. This action log has been submitted to ROBLOX Error Code:267” - Bug

bc i need it to get to the newest update

To get it to the latest update you are suppose to publish not migrate

If you updated something then this happened, remove it from your studio and report it.
Be very careful with plugins and models other people have created.

I did not add anything I just grouped a Building then pressed it

1 Like

oh and minimic is correct. Error code 267 means game dev kicked you out of the game not roblox banned you. The ban message was written by a troller

It doesn’t matter if you did. Just check ALL your model and scripts and plugins.

1 Like

It is likely an anti-exploit script/module you use that has been confused by players being removed as part of the server shutdown.

Does your game contain any anti-exploits?

It’s not from Roblox themselves as it’s called Roblox not ROBLOX, and the “You’ve been kicked from the game:” is there to indicate it’s a developer-driven action.

1 Like

Check all your scripts to search any possible infection.

2 Likes

You are most likely using CarbonEngine (CE), which is basically a framework for weapons. It has a few lines in the code where it kicks the player based on incorrect arguments.

Example:

if not L_171_arg8 or L_171_arg8 ~= 'Auth' then
		L_164_arg1:Kick('Exploiting is a bannable offense. This action log has been submitted to ROBLOX.')
end;

Make sure it is up to date.

3 Likes

I think the easiest way to detect which script is doing this is run the game in studio. Since the Kick() function doesn’t work in studio, it will print an error in the output.

1 Like

Kick does work in Studio. Studio operates like a normal game server, except with no latency and all physics are handled by you, the client. It also has a different security level from normal game to my memory, but that’s an entirely different topic.

1 Like

This is either a free model virus or your anti-exploit is acting up. Actual ban logs don’t look like that. I suggest searching all your scripts for ‘This action log has been submitted’ then finding it and deleting it.

1 Like

Did you do something BEFORE grouping the building? Like adding a model, allowed script injection from a plugin, etc, etc?

Roblox would not use a normal kick message, they would probably use something more secure with SecurityLevel, and you wouldn’t even know about it until you got the ban message on your home page on roblox.

You have a virus in your game.

Do yourself a favor, and in studio, Press Ctrl+Shift+F.
Now, type :Kick in the textbox that comes up.

Any instances that come up with that code, delete.

Then, check all of your plugins. You likely have plugins that impersonate real ones, when they actually inject harmful elements into your game.

People say to delete anything that has :Kick() in it and delete it without looking at the code first, which is just bad advice considering how Kick is a core function in every moderation based system

My advice is to look at any plugins you have first, share a list with us so we can help.

I would also advise the games owner to open any Scripts/ModuleScripts (kick doesn’t work in a local) and press Ctrl/CMD + F and type :Kick().

If you have any requires or getfenvs, delete them as well, I would save a copy whilst doing this incase you end up affecting core functions of your game.

If that was the case, then the creator would know not to delete it. It’s common sense.

But say if someone who doesn’t know anything about studio read that, they would delete all the scripts that have :Kick() in it, which if it’s from some admin system, it would break

If that were the case, they wouldn’t have an admin system.
If they have a toolbox admin system, it would require a module.
Again, common sense.