Skip to main content

How to Avoid Getting Farted On in WHO FARTED?

What the fart-on-you threat means in WHO FARTED?, what happens when it lands, evidence-backed avoidance options, and what to recheck after updates.

Quick answer

Being farted on is the danger WHO FARTED? is built around: one hidden player — the secret farter — wins by landing a fart before innocents organize and identify them, and everyone else must find them before getting farted on. The threat is a hidden player in your lobby, not a scripted map hazard, and no dodge, counter-move, or defensive item is confirmed to cancel a strike.

  • WHO FARTED? is a Roblox Survival / 1-vs-All party experience from Badass Experiences; lobbies cap near 10 players.
  • Finish every task and survivors win the round outright — no identification required.
  • Press the emergency button to open a team discussion and vote; a wrong vote fails the round and leaves the threat active.
  • Avoid dead-end trips with unverified players — stay visible and push a vote when someone is about to be isolated.
  • React to in-round warnings: power cuts, same-level alerts, and 'farter on the loose' callouts.

What happens when the Farter gets you

Gameplay footage of the experience shows what a fart does when it lands: it eliminates the player. Survivors state the stakes up front — "If we get farted, we're dead" — and casualties are shown collapsed on the floor: "Look at how we're all unconscious. We all fell and died." One elimination is described as a player sniffing the fart and dying from how terrible the smell was.

Eliminated players leave bodies that others can discover and ask about ("has anyone spotted a dead body?"). The same footage shows the Farter moving away from the body before anyone gets suspicious — a behavior you can watch for when a strike happens near you. Note that "dead" versus "unconscious" wording comes from player commentary, not in-client text; check the game's own elimination labels each patch.

Your round levers: tasks, timer, emergency button, voting

These outcomes are as observed in gameplay footage and commentary, plus one warning repeated by the roles hub:

Comparison

Comparison
Survivor ActionObserved Outcome
--
--
--
--
--
--
--

Warnings that the Farter is nearby

Footage shows three in-round cues that the Farter is close:

Checklist

  • Power cut + Farter warning

    An outage announced together with the Farter: 'Power's out. The farter is nearby.' Survivors in footage rush to find and repair the power box, after which 'the power's back on.'

  • Same-level alert

    'The suspect is on the same level as us.' — the suspect shares your level or floor.

  • 'Farter on the loose' callout

    'Uh-oh, that means the farter is on the loose and he's nearby.' — the players treat it as the cue to lock in on tasks or identification.

Don't get isolated

The game's fan-wiki guides (unofficial resources that document verified systems plus genre-solid social deduction advice) frame the fart strike as an isolation play. Among the positioning tells they list for the Farter is "steering duos into dead-end spaces," and they name the danger window explicitly: "The farter is about to isolate someone and the lobby is distracted." Their concrete positional advice for survivors is to "Pause in a contested area with a trusted teammate watching your back." The wiki's Farter role page gives the design reason: "Isolation windows matter in most 1-vs-all party designs."

For a player who does not want to be the victim: avoid dead-end trips with unverified players, stay where others can see you, and treat the moment someone seems about to be isolated as the moment to push a vote rather than drift off alone. One caveat — gameplay footage also shows the Farter going after somebody far from the group, and silent hiding did not stop a searching Farter either. Positioning lowers exposure the way the guides model it, but neither distance nor company is stated to remove the risk. Each patch, check in-game whether strikes can ignore range or line-of-sight in the current version.

What targeted players did in the moment

These are behaviors observed in gameplay videos — treat them as player responses, not confirmed mechanics:

Tips

Stay quiet while it searches — but don't trust silence

Players hid silently and moved only after the Farter left ('just don't make no sounds' … 'all right boy he's gone'). In the same footage, silence did not guarantee safety: the searching Farter sniffed players out — 'hello I smell you from upstairs.'

Relocate instead of waiting for the strike

'let's get the hell out of here'; 'I won't sit here waiting to die.' Observed player responses in footage, not a documented defense.

Hit the emergency button immediately after witnessing a fart

Hesitation can lose the race: 'NO, I WAS GOING TO TURN THE emergency button on, but he came just in time.'

Treat the red-seat rule as an individual precaution

One player's stated precautions were avoiding eye contact and red seats ('I'm going to avoid being in a red seat.'), but the video never explains the red-seat rule — an unverified personal habit, not a documented mechanic.

Recheck after updates

Threat and avoidance details are version-sensitive. The wiki's identification guide warns that "Exact UI labels can change after patches, so always read the on-screen objective," and because layouts can update, positioning reads should be judged relative to the current round — "not a memorized tile name from a YouTube short." The Farter role page adds that "Exact ability UI may evolve" and that any in-client charges, prompts, or timers override generic advice; it deliberately declines to state Farter cooldowns, and no strike range, cooldown, charge count, or wind-up timer is documented anywhere — don't plan around numbers like that.

The wiki's links hub sets the general rule for conflicts: "Game mechanics can change without notice; always prefer in-client text and developer posts when they disagree with a guide." This is a young August 2026 release with a fast-shifting meta, so recheck the threat effect, warning labels, and these avoidance behaviors after each update — including whether eliminations currently read as "dead" or "unconscious" in the client.