Addressing Misinformation: How Trap Game Detection Actually Works

A video has been circulating that criticizes Rotector's trap game detection system, claiming it produces false positives and that our team is dishonest. The video runs 25 minutes and makes a lot of claims. We are going to address every single one of them with evidence, much of it from the creator's own words in our Discord server.

This post also serves as a case study. When someone is caught by the trap game system, a common pattern follows: denial, shifting stories, and attempts to redirect the conversation away from the evidence. This is a detailed look at what that process looks like in practice. As you read, pay attention to a recurring pattern: every time a claim is addressed with evidence, the response is not to engage with that evidence but to change the subject, introduce a new person, or tell a different version of the story. If our system had a real flaw, we would fix it. We invite you to read the evidence below and decide for yourself.

If you are just here to understand how trap games work, the first section below covers everything you need to know. The rest of this post is a detailed response to the video's claims.

What Are Trap Games?

In February 2026, we partnered with osuxty, the creator of Destroyer of Worlds, currently the largest database of its kind with over 500,000+ unique flagged Roblox users. osuxty's data is not only used by Rotector. It has also been adopted by EASI (announced by RubenSim on X) and TASE/Mococo, who uses it for appeals. These are other safety initiatives that independently evaluated the trap game methodology and chose to integrate it.

One of osuxty's most effective tools is the trap game system, also known as honeypots.

Here is how they work:

1. Selfbots advertise fake condo game links inside real condo Discord servers, the same servers where people share actual condo content. Each post includes a game link and a KEY containing the access code.
2. A user in one of these condo servers sees the link, clicks it, and joins the Roblox game.
3. The game presents a code entry screen with a question (e.g., "How many light-years is the universe in diameter?"). This question is a Roblox compliance measure only. Answering the question correctly does nothing. The actual code is a lengthy numerical access code distributed alongside the game link in the condo Discord server.
4. The code cannot be guessed. It is too long and too random. You must obtain it from the condo Discord server where the game was advertised.
5. After entering the correct code, the user enters a waiting room with a countdown timer and instructions saying they will be teleported to the "main game." This teleportation never happens. It is a honeypot designed to waste their time and log their activity.
6. The system logs the user's join time, leave time, session count, and total playtime.

These trap games are not real condo games. They contain no inappropriate content whatsoever. They exist solely as honeypots to identify users who actively sought out condo content through Discord servers. The "main game" they promise to teleport you to does not exist.

The critical point: you cannot be logged by this system without entering the correct access code. The code is only available in condo Discord servers. If you were never in a condo Discord server, you would never have the code, and you would never be logged.

How the trap game and access code are advertised inside condo Discord servers

The in-game code entry screen. The question is a Roblox compliance measure. Answering it correctly does nothing. The real code is a lengthy number from the condo Discord server.

What the game page looks like on Roblox before joining

After entering the code, a "Generate the Game" button appears

The waiting room with a countdown timer. The "teleportation" to the main game never happens.

What "Mixed" Status Means

Before diving into the specific claims, it is important to understand what the video creator was flagged as at the time of the video. He was marked as "Mixed."

Mixed status means:

"This user has been linked to inappropriate content, but lacks sufficient evidence for Roblox action. They could also be a victim. Exercise caution."

This is the most lenient flag in our system. It exists specifically for cases where someone might be a victim rather than a willing participant.

In this case, his Mixed status was actually the result of a bug in our initial data import. The 0-minute playtime display caused the system to not recognize his full 35-minute session. Once we identified and fixed this bug, the actual server logs confirmed a 35-minute session, and his status was updated to Confirmed after reviewing all evidence, including his own admissions in our Discord server.

His Rotector profile at the time of the video, showing Mixed status with 40% Condo Activity confidence. This has since been updated to Confirmed.

Claim-by-Claim Response

"The games are public, anyone can join and get false flagged"

The Roblox game itself is technically accessible on the platform. But being able to join the game is not the same as being logged by the system.

You are only logged if you enter the valid access code. The code is:

• A lengthy numerical string that cannot be guessed
• Only distributed in condo Discord servers alongside the game link
• Completely separate from the in-game question. The game shows a trivia question as a Roblox compliance front. Answering the question correctly does nothing. The real code is the long number from the Discord server.

If you stumbled onto the game from the Roblox discover page, you would see a code entry screen with a trivia question, have no idea what the actual code is, and leave. You would not be logged. The system does not flag random joiners.

Server logs showing a player's leave event. Logging only occurs after a valid code has been entered.

"I never entered a code"

This is the central claim of the video, and it falls apart under his own words. His story about the code changed multiple times across three days in our Discord server.

When asked why he spent 35 minutes in the game, his answer was that he was "curious."

Being "curious" does not explain how he got logged. Curiosity alone cannot get you past the code gate. You can join the game and stare at the code entry screen all day, but without the lengthy numerical access code from a condo Discord server, the system will not record you. The fact that he was logged means he had the code. The fact that he stayed 35 minutes means he was not just passing through.

When osuxty then told him "u have to input a code to access anything," his reaction was confusion and denial:

He questions whether there was a code, then claims not to remember one. But the system recorded his 35-minute session, which is only possible after entering the correct code.

In a separate incident involving a different condo game labeled "Temple Run 2," he admitted to entering a code his friend gave him. Unlike our trap games (which are honeypots containing no inappropriate content), this "Temple Run 2" was an actual condo game disguised with an innocent name:

A different game from the trap game, but it shows a clear pattern: he obtained access codes for condo games through his social circle.

His story continued to shift over the following days. On February 20, he started claiming he never even opened Roblox during the time in question. This is a complete reversal from his earlier admission of being in the game and being "curious" about the timer:

Three days later, he goes from "I was curious about the timer" to "I never even opened Roblox." He also asks to redo his appeal, which he had access to the entire time.

After this blog post was published, he responded in Discord. His response introduces a new version of events and raises questions that deserve direct answers.

After reading the blog post, he now remembers being in the trap game room, contradicting his earlier "I never opened Roblox" claim.

He asks why the blog does not prove he joined a condo Discord server, calling it one of his main arguments from the video. We address this below. He also complains that people who responded to his video went through his friend's account instead of addressing his arguments. Then he reverses his "I never even opened Roblox" claim entirely: "now i remember, i do finally remember joining a game in that room with a 'skip time' button." He remembers the room. He remembers the timer. But his new defense is that the code gate did not exist: "there was no fucking key thing in that game, i joined into it and it just plopped me straight into the game."

He concedes his story was inconsistent, remembers the room and timer, but blames a scripting error for bypassing the code gate.

He says the blog "brings up issues i literally explained in the video." The blog addresses his video claims, but with evidence he did not have access to at the time: his own Discord messages, server logs, and timestamps.

He then concedes that his earlier statements were all over the place. He remembers the room and the "skip time" button but insists there was no code, blaming a scripting error. He says he will check if he has footage from January 30, the date of his second session, implicitly confirming the dates in our logs are accurate. He also asks why we have not checked Discord "joined server" logs to prove he was in a condo server.

But here are the facts:

The code gate cannot be bypassed. We have reviewed the trap game's source code. The way it works is straightforward: the logging system is completely turned off when you first join the game. It only activates after a player enters the correct access code. Until that happens, the system does not record anything. No joins, no leaves, no playtime. The code entry screen also cannot be skipped or closed. It stays on screen and checks every half second to make sure it has not been removed or hidden. There is no scripting error, no exploit, and no edge case that would let a player reach the timer room without entering the correct code. If you are in that room, you entered the code.

local screenGui = script.Parent
local mainFrame = screenGui:WaitForChild("MainFrame")
local answerBox = mainFrame:WaitForChild("AnswerBox")
local submitBtn = mainFrame:WaitForChild("SubmitBtn")
local replicatedStorage = game:GetService("ReplicatedStorage")
local quizCompleteEvent = replicatedStorage:WaitForChild("QuizCompleteEvent")

local CORRECT_ANSWER = "XXXXXXXXXXXX" -- lengthy numerical access code (redacted)
local quizFinished = false
local loopActive = true

-- This loop runs every 0.5 seconds and forces the code screen
-- to stay visible. It cannot be closed, hidden, or removed.
task.spawn(function()
    while loopActive do
        if not screenGui.Enabled then screenGui.Enabled = true end
        if not mainFrame.Visible then mainFrame.Visible = true end
        if not answerBox.Visible then answerBox.Visible = true end
        if not submitBtn.Visible then submitBtn.Visible = true end
        task.wait(0.5)
    end
end)

local function checkAnswer()
    if quizFinished then return end
    local input = answerBox.Text

    if input == CORRECT_ANSWER then
        -- Correct code: notify the server, hide the screen, proceed
        quizFinished = true
        loopActive = false
        quizCompleteEvent:FireServer()
        screenGui.Enabled = false
    else
        -- Wrong code: flash the input box red and reset
        answerBox.Text = ""
        answerBox.BackgroundColor3 = Color3.new(1, 0, 0)
        task.wait(0.2)
        answerBox.BackgroundColor3 = originalTextBgColor
        answerBox.Text = "[ ANSWER HERE ]"
    end
end

submitBtn.MouseButton1Click:Connect(checkAnswer)

local quizCompleted = false
local loggingActive = false

-- This function sends player data to the logging system.
-- It does NOTHING until quizCompleted is true.
local function sendData(url, embedData, content)
    if not quizCompleted then
        return
    end
    -- ... sends player data to the logging system ...
end

-- This only fires when a player enters the correct code.
-- It flips the flag that enables all logging.
quizCompleteEvent.OnServerEvent:Connect(function(player)
    if loggingActive then return end
    loggingActive = true
    quizCompleted = true
end)

-- Player leave handler: only logs if quizCompleted is true
Players.PlayerRemoving:Connect(function(player)
    local joinTime = playerJoinTimes[player.UserId]
    local playTime = nil
    if joinTime then
        playTime = math.floor((os.time() - joinTime) / 60)
    end
    if quizCompleted then
        logPlayerActivity(player, "leave", playTime)
    end
end)

The code IS the proof of being in a condo Discord. He asks for proof that he joined a condo Discord server. The access code is only posted inside condo Discord servers by selfbots alongside the game link. It is a lengthy numerical string that cannot be guessed. If you entered the code, you obtained it from a condo Discord server. There is no other source. We also have no way to verify his condo Discord activity. We do not know his alt accounts, and even if he shared them, there is nothing stopping him from leaving out the ones that matter. If his accounts had Bloxlink or Rover verification linked, the system would have already flagged the connection. Regardless, the code entry itself is the proof. No Discord lookup is needed.

He says the team gave "vague answers." This blog post, with server logs, timestamps, and screenshots of his own words, is the opposite of vague.

To summarize his shifting story:

1. "I was curious" about the timer, was talking to people in the game
2. "I don't remember a code"
3. "I never even opened Roblox"
4. "I do remember the room, but the script must have bugged"
5. "I joined to see what would happen for 35 minutes, there was no code" (addressed in His Continued Response)
6. "My friend joined me and can confirm there was no code" (addressed in His Continued Response)

Each version contradicts the last. The one thing that has not changed is the server logs: he entered the code, and he stayed for 35 minutes.

"It was only 0 minutes, probably a misclick"

In the video, he fixates on a "0 minutes" display as proof it was accidental. Here is what actually happened:

The "0 minutes" was a bug in our initial data import from osuxty's logs. It represented unknown playtime data, not an actual 0-minute session. He was among the first users to surface this display issue, and we have since fixed it. When we checked the actual server logs, the real data told a very different story:

• First session: Joined 9/30/2025 at 11:26 PM, left 10/1/2025 at 12:02 AM. Total playtime: 35 minutes and 51 seconds.
• Second session: Joined 1/29/2026 at 11:41 PM, left 1/29/2026 at 11:42 PM. Total playtime: less than a minute.

All timestamps are in GMT+8.

Server logs showing all of his sessions. The first lasted 35:51 minutes. The second was under a minute.

The trap game has a countdown timer. He stayed for over 35 minutes, meaning he waited past the full countdown before leaving. In our Discord, he confirmed this himself:

He admits waiting through the timer and chatting with other people in the game. Nobody who is "just curious" waits 30+ minutes for a game to start.

He also joined a second time. Even if that second visit was brief, he still had to enter the access code again to be logged.

"My footage proves I wasn't there"

He claims to record all his gaming sessions. He presented footage of himself watching a friend play a Steam game around the same timestamp as his flagged trap game session. In our Discord on February 20, he said "i was deadass watching my friend play something on steam" and "THE FOOTAGE PROVES THAT."

There are several problems with this:

• He does not have footage of the actual trap game session. Despite claiming to record everything ("i like to record a lot when im playing with friends"), the one session that would prove his innocence conveniently does not exist.
• Timezone differences were pointed out to him. The timestamps he was comparing may not have been in the same timezone.
• He could have been on his phone. When asked if he owns a mobile device, he confirmed he owns two. Roblox runs on mobile.
• The footage he shared shows him doing something else. It does not prove he was not simultaneously logged into a Roblox game on another device.

When asked if he records every game session, he confirms he does. Yet the one session that would prove his innocence is missing. He also says "i don't remember a code + timer" and admits "i still fucked up joining my friend though."

When community members pointed out these issues, he became increasingly hostile rather than addressing them.

"They only look at my Steam and Newgrounds, not my Roblox"

This is a misrepresentation of what happened.

The detection system flagged him based solely on trap game entry logs. That is it. No one looked at his Steam or Newgrounds to flag him.

During the Discord conversation, community members (not the detection system, not the development team) brought up his Steam reviews and Newgrounds activity as part of the discussion. He was frustrated that people were looking at his other platforms instead of his Roblox account. But the flag was based on the trap game logs, not his Steam or Newgrounds. What community members found on other platforms was part of the public conversation, not part of the detection process.

He did acknowledge his Newgrounds content was problematic:

He admits his Newgrounds content is "cooked" but argues it is irrelevant to Roblox. The detection system agrees: the flag was based on trap game logs, not his activity on other platforms.

"They banned me because they couldn't disprove my argument"

This is not what happened.

He went to the general chat channel, not the formal appeal process. He became confrontational and hostile in a public channel with other community members. He was banned for disruptive behavior, not because anyone could not address his arguments.

A formal appeal process exists and was available to him the entire time. He was aware of it and was working on an appeal:

He had a path to resolution through the formal appeal process. He chose to argue in general chat instead.

"There are false positives, normal people are getting flagged"

The code-gating system makes false positives from random game discovery structurally impossible. To be logged, you must:

1. Be in a condo Discord server
2. See the trap game link and access code posted there
3. Join the Roblox game
4. Enter the lengthy numerical code (not the trivia answer, the actual code from Discord)
5. Get logged by the system

There is no shortcut. There is no way to skip the code. There is no way to accidentally end up in the logs.

He showed other flagged accounts in the video, claiming they were innocent. One example was a user named "wenz," who was flagged with 83% Condo Activity confidence for entering a trap game with 38 minutes of total playtime. That account was reviewed and confirmed as Unsafe by human moderators.

The account he claimed was "a completely normal person." It was reviewed and confirmed as Unsafe.

Server logs for the same account showing 38 minutes of playtime in the trap game

"Hunters are hypocrites who play condo games themselves"

In the video, he criticizes the "Hunter" role, volunteers who enter condo spaces to identify harmful content and users.

This is like criticizing undercover law enforcement for being in the same room as criminals. Hunters have authorized access and a specific purpose: to identify and log users engaged in harmful behavior. Their presence in these spaces is deliberate, documented, and purposeful, not recreational.

The distinction should be obvious: a hunter enters a condo server to protect children. A condo player enters to consume inappropriate content on a kids' platform.

The Full Picture

When you put all the pieces together, the picture is clear.

He entered a code-gated trap game twice. The first time, he stayed for 35 minutes and 51 seconds, waiting past the full countdown timer and chatting with other people in the game. The second time was under a minute. Both sessions required entering the access code, which can only be obtained from condo Discord servers.

When confronted about the code, his story kept changing. First he said he was "curious" about the timer and that he was "talking to people in game." Then he questioned whether there was even a code. Then he claimed he never even opened Roblox. Then, after reading this blog post, he reversed course again and admitted he does remember the room with the timer, but claimed the script must have bugged and let him in without a code. Then he changed it again to say he joined to see what would happen for 35 minutes and there was simply no code. Then an unnamed friend appeared who could supposedly confirm there was no code. The code gate cannot be bypassed. Six different stories, zero evidence for any of them.

Separately, he admitted that a friend gave him the code for a different condo game disguised as "Temple Run 2," and entered it. This shows he was not some random player who stumbled into a trap. He had friends actively sharing condo game codes with him.

He claims to record all his gaming sessions, but the one session that matters, the 35-minute trap game session, conveniently has no recording. Every other session from around that time? Recorded. The one that would prove his innocence? Missing.

Throughout the Discord conversations, the discussion kept going in circles. Community members brought up his Steam reviews and Newgrounds content. He kept showing random game footage and recordings from other days. But none of it addressed the two simple facts at the center of this: he entered the code, and he stayed for 35 minutes.

Despite all of this, the system initially flagged him as "Mixed," the most lenient classification, giving him the benefit of the doubt. He had access to a formal appeal process. Instead, he chose to argue in general chat, got banned for being disruptive, and then made a 25-minute video misrepresenting the entire situation.

His Continued Response

After we published the update above, he continued responding with additional claims, including the fifth and sixth versions of his story. First: "I joined to see what would happen for 35 minutes, there was no code, and I left." Then: "My friend joined me in the game and can confirm there was no code." We address the substantive claims here.

"My friend was in the game and wasn't logged"

In the video, he admits he was on the game with a friend and claims there was no code, just a timer. The friend also appeared in the video backing this claim. Neither has provided any evidence beyond saying "there was no code." It is also unclear whether this is the same friend who gave him the Temple Run 2 code, a different friend, or multiple people. Regardless, saying "there was no code" does not make the code disappear from the source code.

This friend also did not need to be in the game at all. Condo Discord servers post the game link and access code together. Someone in those servers could simply forward the link and code to him without ever joining the game themselves. We have no way to verify any claims about this friend until they come forward and identify themselves.

If there was no code, why wasn't that his first story?

His original response when confronted about the 35-minute session tells us everything. At 9:47 PM on February 17, someone asked him why he spent 35 minutes in the game. His answer: "it was a TIMER, i was curious." He talked about the timer room naturally, as if being there was unremarkable. No mention of a missing code. No confusion about how he got in.

Six minutes later, at 9:53 PM, osuxty told him "u have to input a code to access anything." Only then did he react: "?????? there was a key" and "i don't remember there being a key?????????"

If there had genuinely been no code, that would have been the most notable part of his experience. His first response would have been "I joined this game and there was just a timer room, no code or anything." Instead, he described the timer room as if entering the code was routine. The "no code" defense only appeared after he learned the code mattered.

"Other games exist without a code gate"

He has since found other Roblox games with timer rooms and "Skip Time" buttons that do not require a code. He argues he was in one of those, not osuxty's.

There is only one version of osuxty's trap game. It has had a code gate since 2024, well before his first session in September 2025. The screenshots in this blog post, the code entry UI, the timer room, the "Generate the Game" button, are all from that game. This is the game that logged him. It is the only known fake condo that uses a code gate.

The other games he found are either real condo games or unrelated fakes built by someone else. They were not built by osuxty, they do not feed into osuxty's database, and they did not produce the logs shown in this post. His sessions were recorded by osuxty's system, from osuxty's specific game, through osuxty's code gate. Finding other games that look vaguely similar does not change that.

"Why would I use my main Roblox account but an alt Discord"

He argues it makes no logical sense to use his main Roblox account (linked to all his socials) for condo games while using an alt Discord account to hide from detection.

This is exactly why trap games work. People are careful on Discord because they know condo servers get reported and monitored. Many use alt accounts, avoid linking Bloxlink or Rover, and keep their condo activity separate. What they do not expect is that a Roblox game itself could be a trap. From monitoring condo games, our team has seen countless players use their main Roblox accounts as if they are invincible, even accounts linked to their real socials. The trap game system exists because people assume they are safe on the Roblox side. That assumption is the entire point.

"I'm not flagged on EASI, rocleaner, or TASE"

Different systems use different thresholds because they integrate the data differently. When we partnered with osuxty, we worked closely with him over multiple conversations to understand the data, ask questions, and determine the right thresholds. We use both join count and playtime as signals, which is why a 35-minute session with 2 joins was enough to flag him here. EASI, by contrast, set a 3-join minimum without a playtime override. osuxty himself noted to us that their integration was not using the data as effectively. Being below another system's threshold does not mean he is innocent. It means their threshold is higher and their implementation is less thorough.

"Your community posted fan art of my avatar"

He claims the Rotector community posted inappropriate fan art of his Roblox avatar. We trace the fan art back to someone in his own social circle and examine their public activity across multiple platforms:

What He Still Has Not Answered

Throughout all of his responses, several questions remain unaddressed:

• A friend appeared in the video backing his "no code" claim. Is this the same friend from the Temple Run 2 incident, or someone else? Why has this person not come forward independently with any evidence?
• If there was no code, why was "no code" not the first thing he said when confronted? When first asked about the 35-minute session, he said "it was a TIMER, i was curious" without any mention of a missing code or confusion about how he got in. The code only became an issue after osuxty told him one existed.
• If his friend was also in the game and there was no code, why was he logged but his friend was not? (See "My friend was in the game and wasn't logged" above.)
• We have reviewed the source code. We have tested the system. We have found no flaw. If the code gate can somehow be bypassed, show us how. The other games he found without code gates are not osuxty's and do not explain the logs.
• Why does every recording he has conveniently exclude the one 35-minute session that would prove his innocence?
• His story has changed six times. Why? (See "I never entered a code" and His Continued Response for full details.)
  1. "I was curious" about the timer, was talking to people in the game
  2. "I don't remember a code"
  3. "I never even opened Roblox"
  4. "I do remember the room, but the script must have bugged"
  5. "I joined to see what would happen for 35 minutes, there was no code"
  6. "My friend joined me and can confirm there was no code"

He has had every opportunity to answer these. We have read every one of his responses. The vast majority do not engage with the evidence presented here. They repeat claims already addressed in this post, attack community members, or shift to topics unrelated to the trap game detection. The few substantive points he has raised are addressed in the sections above. First it was the code. Then the timer. Then he never opened Roblox. Then the script bugged. Then an unnamed friend. Then other games. Then community conduct. Then fan art. Each new thread either falls apart under scrutiny or has nothing to do with the trap game detection at all. He is not addressing the evidence. He is deflecting from it.

The more he responds, the worse his position gets. At this point, the honest path forward is to stop digging and acknowledge what happened.

Moving Forward

We take accuracy seriously. When the "0 minutes" display bug was brought to our attention, we fixed it. When users appeal through the proper channels, we review their cases. That is how a responsible system works.

Our partnership with osuxty and the trap game system is one layer of a multi-layered detection approach. The code-gating ensures that only users who actively sought out condo content and obtained an access code from condo communities are logged. This is by design, and it is why false positives from random game discovery are structurally impossible.

After reading this post, he requested a direct conversation with our team. We have decided not to engage further. We have addressed every claim from the video, responded to every point raised afterward, published the source code, and shown the server logs. There is nothing left to discuss.

Rotector is a small team, and this has consumed time we would rather spend protecting kids. We have nothing further to add.

We wrote this post because transparency matters. If we were wrong, we would say so. We are not wrong here.