Roblox error code 267: why you were kicked and what you can do

Roblox error code 267 is generally described as a kick from one specific experience, not a ban on your whole account. Try another game to confirm, stop using any exploit or injector tools, and ask the game's creator about the removal. Developers who see it in their own playtests should search their scripts for kick code.

Applies to:RobloxPlayer client; also reported in Roblox Studio playtests
On this page

What it means

Error 267 appears when you are removed from a Roblox experience. The message is usually "You were kicked from this game". Sometimes a reason is shown, and often it is not.

Guides on the topic describe it as something the experience did, through its own moderation or an admin or anti-exploit script, rather than a ban on your whole Roblox account. The Roblox help pages were not available while this article was researched, so this explanation comes from third-party guides and a developer forum thread, not from Roblox documentation.

The practical consequence: reinstalling Roblox is unlikely to help if only one game is affected. The first job is to find out whether the problem is that one game or something wider.

Symptoms and causes

You are likely dealing with this problem if:

  • You are disconnected from one experience with error 267, sometimes with a reason message and sometimes without.
  • Other Roblox experiences still load and play normally.
  • Developers may see the same error during a playtest in Roblox Studio.

The usual causes, most common first:

The experience's own kick or ban
An admin script or the developer's moderation removed you. This is the most common cause according to the sources reviewed.
Account restrictions set by the game
Some games limit who can join, for example by minimum account age. This varies from game to game.
Anti-exploit false positive or exploit tools
Anti-cheat scripts can kick players they flag, and using exploit or third-party tools can trigger it.
Restricted or locked experience
The experience may not be open to you.
Scripts inside your own place (developers in Studio)
A stray kick script, a backdoor or illegal script in the place, or a script that destroys the Player instance can show the same error. The DevForum thread on this never reached a confirmed fix.

How to fix it

Work through these in order. They start with the quickest, safest checks and move to deeper repairs; stop as soon as the problem is gone.

1.Try a different experience

Easy

This separates a single-game kick from a wider problem with your device, network or account.

  1. Open a different Roblox experience and join it.
  2. If it works, the cause is most likely the first game's own rules or moderation, so continue with the next fixes.

2.Read the kick reason and stop what triggered it

Easy

When the game gives a reason, it usually names the rule you broke or the system that flagged you.

  1. Note the exact text shown with the 267 message.
  2. If you use any exploit, injector or similar third-party tool with Roblox, uninstall it before trying that game again.
  3. Check the game's page description for any entry requirements, such as account age, and try again later if you do not meet them.

3.Contact the experience's creator

Easy

Kicks and bans inside an experience are normally decided by its creator, so they are the people who can review one.

  1. Open the game's page on Roblox and look for a linked group or Discord server.
  2. Politely ask why you were removed and whether it can be reviewed. Never share your password or login codes with anyone who asks for them.

4.Developers: find the kick in Studio

Advanced

If you see 267 in your own place during a playtest, a script in the place is probably removing the player.

  1. In Roblox Studio press CtrlShiftF to search all scripts. Search for the kick reason text shown in the error and for :Kick(.
  2. Review every script in the place for backdoors or code you did not write, and remove anything suspicious.
  3. Check the settings of any anti-exploit system you use, since it may be flagging your own test player.

Check that it worked

  • The experience that showed error 267 now lets you join and stay connected.
  • Or, if the removal stands, other experiences work normally, so your account and install are fine.
  • In Studio, your playtest runs without the player being kicked.

If it still fails

  • If only one game fails and the creator does not respond, the removal probably stands and you will need to play other experiences.
  • If every game fails, the cause is likely not a game-level kick. Read the error text carefully and compare with error 262 or error 279, which are different Roblox errors.
  • Look up error 267 on the Roblox help site and contact Roblox Support if your whole account seems affected.

Questions

Does error 267 mean my Roblox account is banned?

Not necessarily. It is described as a removal from a single experience. If other games work normally, your account is not affected.

Can I appeal a game's ban?

The creator of the experience is the first person to ask, usually through its group or Discord. Roblox Support is the place to go if your whole account is affected.

Sources

  1. Error code 267 in Roblox Studio (community thread) · Roblox DevForum (community content)
  2. Roblox Error Code 267 | Why was I kicked or banned? · GameRevolution