2026-10-03
Latest recheck of the family evidence and badge-confirmed responses.
Compare the documented encounter families by where they appear, how they are detected, and what response each needs. Deliberately unordered: no verified power, rarity, or spawn-rate data supports S/A/B ranks for this game, so this page compares surfaces instead of faking a hierarchy. Checked 2026-10-03.
Latest recheck of the family evidence and badge-confirmed responses.
Customer appearance, table area, camera feeds, and walkways.
No verified power, rarity, or spawn-rate data supports them.
Confidence describes the current documentation, not how dangerous or rare an encounter is.
Community videos show several face-focused examples. Compare the full customer, not one feature in isolation.
A named community video chapter makes this an easy family to locate, but its exact trigger is not documented by the creator.
A current community video groups four camera examples. Treat them as places to inspect, not a complete catalog.
Sources: community compilations for detection, official badges for the confirmed responses. Checked 2026-10-03.
| Family | Where it appears | How to detect | Documented response |
|---|---|---|---|
| Face anomalies | The customer in front of you | Compare the whole customer against a normal guest — proportions, expression, posture — rather than one feature. A slightly odd single feature can be fine while a mismatch across the full model is the real tell. | Serve customers who read normal top to bottom; refuse the ones that do not. |
| Table Monster | The table area | A named table entity that behaves unlike a regular guest occupies table space. | Feed it — do not serve it like a customer and do not bat it. Feeding it correctly pays the Yummy badge. |
| Camera anomalies | The security-camera monitor feeds | A feed that looks disturbed, altered, or simply wrong signals an active camera anomaly. Cycle through every feed; one glance is not enough. | Scan all feeds habitually during service lulls instead of only reacting to obvious changes. |
| Path-Blockers | Walkways between counter, tables, and kitchen | Anything obstructing a route you would normally walk. | Clear or handle the obstruction before it costs service time and reviews. |
Badge requirements are developer text — the strongest evidence tier this game offers.
Confirmed by the official Time to Fight Back badge ('Hit a mimic with a bat'). What the Mimic disguises itself as is not documented anywhere public; community footage labels a 'Can We Beat It' chapter that probably matches it, but that link is unproven.
Source: Official badge + Community videos
Confirmed by the official Yummy badge ('Feed the Table Monster'). Feeding — not serving, not batting — is the badge-confirmed interaction. Where it appears across shifts is undocumented.
Source: Official badge
Confirmed as a feature by the official Secret Menu badge ('Serve a customer at the secret menu'). The badge proves the menu exists; its location and contents are not described in any public official text.
Source: Official badge
Read the expanded observation notes.
Select what you noticed in your scene.
Open the current community videos.
See the current exact-game no-code state.
Track the observations you want to check.
The reported encounters are observation categories, not confirmed characters with measurable power.
It shows where a family appears and the current confidence of its community documentation.
No reliable exact-game spawn rates were confirmed.
No. It is an unordered fan reference based on current community examples.
Camera observations: community compilations devote four numbered chapters to them, more than any other family. That reflects documentation volume, not danger — no source ranks families by threat.
Three, through badge requirements: the Table Monster (Yummy badge), the mimic (Time to Fight Back badge), and anomalies that attack customers (Savior badge). Everything else is community-reported organization of scenes the official text never names.
Published spawn rates, threat or reward data, or an official catalog — none of which exist in any public source. Until then, comparing families by observation surface and documentation confidence is the honest version of a tier list for this game.
Use the contact page with the scene description, the shift it appeared on, and a clip or timestamp if available. Reports that check out against a current exact-game recording are added with a new checked date.