WHO FARTED? How to Find the Farter: Clues, Tells, and the Vote Loop

Identify the hidden Farter in WHO FARTED? with in-round clues like briefcase name files and power outages, soft behavioral and movement tells, and the emergency-button discussion-and-vote loop.

Quick answer

In WHO FARTED?, one player is the secret farter and everyone else has to find them before they get farted on. You identify the Farter by collecting in-round clues (briefcase name files, power outages, task progress, the timer), reading behavioral, movement, and friend-stack signals, then pressing the emergency button, holding a team discussion, and voting. A wrong vote clears the accused and leaves the Farter in play, so every read matters in a lobby that caps around 10 players.

Every tell on this page is a soft signal to test live in the current round — the game shows no guaranteed reveal before a vote or round end.
Exact UI labels can change between patches and may say innocent, survivor, or simply imply “everyone else” — trust your current client's on-screen objective text.
Winning as an innocent means identifying and stopping the threat; the Farter wins by staying hidden long enough to land their moment.

In-round clues you can actually check

Tips

Briefcase name files

Briefcases with downloadable files can contain a player's name — a direct suspect lead. In one observed round, a player called out: “Wait, Angel, I saw your name in a briefcase.”

Power outages

When the power is cut, the game directs players to find the power box, and rounds read the outage as the farter being loose and nearby. One outage call noted “The suspect is on the same level as us,” so outages carry proximity information about the Farter.

Task counter

A visible progress readout (one round showed “7 out of 24 tasks complete”) tracks the survivors' task race through the round.

Round timer

Late in the round you must choose between racing tasks and hunting. In one observed round, with a minute left, players weighed “quickly complete the task” against going to figure out who the Farter is.

Behavioral and chat tells — and the mistakes players make reading them

Mistakes to avoid

Problem: Reading a speech-pattern flip as proof — quiet all game, then a perfect essay the moment they're named, or loud all game, then sudden mute when votes open.
Fix: The flip is the signal, not baseline quietness. Judging someone for simply being quiet all game is the mistake — it's the change that deserves a second look.

Problem: Buying over-helping — a player inventing alibis for everyone except themselves.
Fix: Log it as one soft signal and look for corroboration from other players before it counts toward a vote.

Problem: Accepting premature certainty — a suspect named in the first ten seconds with zero observations.
Fix: Treat early hard-calls as low-value and keep gathering information instead of crowning a suspect.

Problem: Getting stuck in deflection loops — every question about a player becomes a joke, a counter-accuse, or “you're throwing.”
Fix: Note the pattern, then test it with one specific, checkable question rather than assuming guilt.

Problem: Counting presentation as guilt — essay defenses that introduce new contradictions, players who never talk then explode when voted, filler-heavy speech, or jittery camera work all “read” guilty.
Fix: Treat all of it as soft. The actual Farter in one observed round flatly denied under pressure (“that was not me who farted”), so denials and calm camera work alone identify nothing.

Mistakes to avoid
Problem	Fix
Reading a speech-pattern flip as proof — quiet all game, then a perfect essay the moment they're named, or loud all game, then sudden mute when votes open.	The flip is the signal, not baseline quietness. Judging someone for simply being quiet all game is the mistake — it's the change that deserves a second look.
Buying over-helping — a player inventing alibis for everyone except themselves.	Log it as one soft signal and look for corroboration from other players before it counts toward a vote.
Accepting premature certainty — a suspect named in the first ten seconds with zero observations.	Treat early hard-calls as low-value and keep gathering information instead of crowning a suspect.
Getting stuck in deflection loops — every question about a player becomes a joke, a counter-accuse, or “you're throwing.”	Note the pattern, then test it with one specific, checkable question rather than assuming guilt.
Counting presentation as guilt — essay defenses that introduce new contradictions, players who never talk then explode when voted, filler-heavy speech, or jittery camera work all “read” guilty.	Treat all of it as soft. The actual Farter in one observed round flatly denied under pressure (“that was not me who farted”), so denials and calm camera work alone identify nothing.

Movement, pathing, and task-behavior signals

These are the patterns that cause hunts to fail when players miss them:

Failure reasons

Problem: Missing shadowing — the suspect trails one player across the map without a clear reason.
Fix: Track who follows whom. Following a suspect is itself a real tactic players use, so note both directions.

Problem: Believing “scout” claims from edge camping near choke points.
Fix: Judge relative weirdness inside this round — layouts update, so a memorized tile name from a YouTube short is worthless.

Problem: Walking into convenient isolation — a suspect steering duos into dead-end spaces.
Fix: Avoid pairing into dead ends with an unverified player, and note who keeps engineering those pairings.

Problem: Accepting fake AFK at high-information moments.
Fix: Run the tracking checklist: who shadows one player, who never enters contested spaces, and who “goes AFK” at convenient times.

Problem: Trusting task theater. In one observed round, the real Farter was “not even trying to make it look like he's doing the tasks. He's just like roaming around.”
Fix: Check whether a suspect's positioning matches actual task locations — and whether they slip away from a fresh body before discovery, as that round's Farter did.

Failure reasons
Problem	Fix
Missing shadowing — the suspect trails one player across the map without a clear reason.	Track who follows whom. Following a suspect is itself a real tactic players use, so note both directions.
Believing “scout” claims from edge camping near choke points.	Judge relative weirdness inside this round — layouts update, so a memorized tile name from a YouTube short is worthless.
Walking into convenient isolation — a suspect steering duos into dead-end spaces.	Avoid pairing into dead ends with an unverified player, and note who keeps engineering those pairings.
Accepting fake AFK at high-information moments.	Run the tracking checklist: who shadows one player, who never enters contested spaces, and who “goes AFK” at convenient times.
Trusting task theater. In one observed round, the real Farter was “not even trying to make it look like he's doing the tasks. He's just like roaming around.”	Check whether a suspect's positioning matches actual task locations — and whether they slip away from a fresh body before discovery, as that round's Farter did.

Friend-stack and voting-pattern tells

Best by use case

Best by use case
Stack Pattern	What It Looks Like	How To Read It
Instant duo clears	“Green is fine” with zero reason, every single time	A classic duo-stack pattern — track whether it repeats under pressure
Mirrored votes	Two friends locking the same name in under a second	Note the pair and watch for the same lock-in next meeting
Peel plays	One friend isolates a random player while the other controls chat	Watch whether the isolated player ends up dead-ended or voted
Joke pile-ons	Pile-ons that always spare the stack	Check who the jokes never target
Lobby-level stack pressure	Solo players bullied into looking guilty; vote leaders who never accept counter-evidence	Forced consensus is a tell — healthy groups disagree on purpose when evidence is thin

One caveat: a noisy stack is sometimes free camouflage and sometimes a death sentence if the room decides the duo is throwing for each other. Read the pattern against the round's actual events.

Step by step: what to do when you have a suspect

Roadmap

1
Press the emergency button
Trigger a meeting the moment you have a reason
- If you witness who farted or find a dead body, press the emergency (red) button — observed play: “I saw who it was. I need to press the button.”
- A player summary of the rule: you're supposed to guess who it was and call a meeting if you see somebody dead.
2
Hold the team discussion
Compare observations and narrow candidates
- The button triggers a team discussion — observed flow: “Nica presses the red button. Okay, we're going to have a team discussion.”
- Compare what each player saw and accuse with reasons: “it's either one of us… we gotta figure it out.”
3
Vote the suspect out
Act on the room's best-supported read
- Vote once a target emerges — observed play: “Press the button and vote out.”
- Exact vote-menu wording isn't documented and can change by patch, so read the on-screen prompts in your client.
4
Read the reveal
Update everyone's status
- A wrong vote shows the eliminated player was innocent — “Grace was not the farter” — and can clear multiple remaining players at once.
- After a wrong vote, “The farter is still among us” — fold the new clears into your suspect list.
5
Watch the parallel failure pressure
Remember the clock while you hunt
- “If we get farted, we're dead” — your positioning matters during the hunt.
- The round timer forces a late choice between rushing tasks and hunting.

Building and ranking a suspect list

Mechanic flow

1
Early game — gather, don't crown a king
Information first; early hard-tunnels rank lower unless the lobby is already collapsing
- Note who pushes for an instant vote and who refuses to share any read at all.
- Watch collisions — who arrives “just after” a scare, who was nowhere nearby — and ask one specific question (“Where were you when X happened?”) instead of “who?” spam.
2
Mid game — keep two to three names max
Rank candidates on what you can defend
- For each name, store what you personally saw, what others claim, and what would clear them.
- Push a vote when you have two or more independent reasons, when the Farter is about to isolate someone while the lobby is distracted, or when a player's story changed in a checkable way.
- Wait when you only have vibes, when the lobby is already mislynching and needs a reset question, or when you're about to confirm a tell in the next few seconds of movement.
3
In meetings — test stories
Extract checkable answers without handing the Farter cover
- Ask binary questions (“Left hall or fountain — pick one”), request a repeat because liars often fail identical retells, and invite a third player to corroborate.
- Stay calm — tilted chat is free cover for the Farter. Save hard tunnels for when two or three independent signals line up.

Baiting the Farter without invented mechanics

Soft bait ideas that need no invented mechanics: walk a semi-public route and see who shadows you; share a slightly wrong detail and see who “corrects” it with impossible knowledge; pause in a contested area with a trusted teammate watching your back. Never bait by throwing the round on purpose or by harassing players outside the game's spirit — keep it clever, not toxic.

Phrasing suspect calls in chat

Short calls work better than novels:

"Suspect A: shadowed B twice, flipped story on spawn. Need eyes."
"Clearing C for now — was with me at mid when the scare hit."
"No vote yet — need ten seconds of pathing on D."

If you use voice, still type key claims so mobile players can follow.

Common mistakes that cost identification rounds

Insta-accusing the quiet kid. Silence is not proof; in joke lobbies, loud players can be louder bait.
Treating the tells above as auto-guilt. They are soft signals, and early hard-tunnels rank lower unless the lobby is already collapsing.
Voting from vibes. A wrong vote wastes the only resource that matters: trust.
Trusting memorized tile names from shorts. Layouts update, so judge relative weirdness inside this round.
Overtrusting other players. Real-round advice: “don't be trusting everybody in this game cuz they might betray you.”

Spectating between rounds

When you're out, don't spam — watch. Note who stops trying once the loudest townie dies, who pivots blame instantly onto the next convenient target, and who looks lost only once their duo partner is gone. If you die or lose early, spectate with purpose: learning who lied helps the next round more than spam-chat. One deliberate drill: spectate a full round without chatting and just study pathing, then carry those notes into the next lobby.

Don't waste time on ESP scripts or auto-win codes

Ignore random “ESP scripts” and executor ads — account risk is not worth a fart joke, and the game's community wiki lists no scripts while warning against executors. No promo codes are confirmed as of September 2026; the real freebie is the group skin. There is no shortcut tool for finding the Farter — the reliable path is the observation-and-vote loop above.

What changes after the Farter is identified

A correct read leads to voting the Farter out: one round ended a suspect's run with “IT IS YOU. I KNEW IT. I TOLD YOU,” followed by “Bean got eliminated” — and eliminated Farters complain, “How did they always figure out I'm the farter?” A wrong vote instead clears the accused and leaves the Farter in play.

Separately, survivors can win by finishing all tasks before the timer without ever identifying the Farter: one round ended with “The survivors won” on task completion, and the Farter's identity was shown only after the round — “the farter was that rainbow dude,” who “was doing a bad job.” So identification-by-vote is one of two visible innocent win paths, the task race runs in parallel, and the Farter's name is revealed at round end either way.