Independent guideA practical guide to mascot horror games, their history and their fan theories.
Cognilusion
Theories

A good mascot horror theory follows an ordered method, not a lucky guess.

This page gives a practical procedure for building and checking theories around games like Five Nights at Freddy's, Poppy Playtime and Garten of Banban.

From claim to checkable claimA funnel that narrows a broad community claim into one falsifiable statement.community claimevidence you found yourselfone testable statementKeep what survives the check; drop the rest.
A theory is worth posting when it has narrowed to something a later chapter could contradict.

The theory checklist in short form

List the raw clues

Write what you saw in plain words. Include the chapter, the room and the exact spot. Save a screenshot or clip where possible.

Split fact from inference

Put what the game shows on one side. Put what you think it means on the other. Keep the two lists apart while you work.

Check outside statements

Look for developer interviews, patch notes or posts. Note the date of each statement. Old comments may not fit a newer chapter.

Test and date the claim

Search for clues that break your idea. Rewrite the claim so it can fail. Add a date and label it as a draft.

Step one: collect the in-game evidence

Every theory begins with something you can point to inside the game. A poster on a wall, a tape recording, a line of dialogue or a small animation all count. Without a source like that, you have a feeling, not a theory. Feelings are fine to share, but they are not evidence.

Collect more than one clue before you build a claim. A single odd detail can be a joke, a bug or a red herring. Two or three related details are much harder to explain away. That pattern is what makes a theory worth writing down.

Use screenshots or short clips where you can. Memory changes a detail over time, especially after you read other people's ideas. A saved image lets you check the exact colour, word or shape later. It also lets other fans verify what you saw.

Write each clue in plain language. Say what it is, where it appears and what it seems to show. Avoid jumping to meaning at this stage. The goal is a clean list of facts before any interpretation begins.

Keep clues from different chapters separate at first. A detail in chapter one may mean something different after chapter three. Mixing them too early can hide the real pattern. Sort them by chapter and by location.

Finally, note how easy the clue is to find. A required item is stronger evidence than a hidden Easter egg. Developers put required items in front of every player for a reason. Optional secrets are often just fun nods.

Step two: note where each clue was found

Location matters as much as the clue itself. A note in a staff room tells a different story than a note in a child's bedroom. The room's purpose shapes how you should read the text. Always write the location next to the clue.

Note the chapter and the exact spot. Say whether the clue was on a wall, inside a drawer or behind a locked door. This detail helps other players find the same item. It also shows how much effort the clue required.

Check whether the clue changes over time. Some games update a poster or a screen after a story event. A clue that changes is usually more important than one that stays the same. Record both versions if you can.

Compare the same clue across chapters when it reappears. A mascot's design might gain a tear or lose a tooth. Those small changes often track the story's progress. They are easy to miss on a single playthrough.

Write down anything the game does not show you. A locked door with no key is a gap in the evidence. Gaps are useful because they mark where a theory must guess. Label them clearly as unknowns.

Keep a simple table if you like. One column for the clue, one for the location, one for the chapter. This format makes patterns jump out. It also makes your notes easy to share with others.

Step three: separate fact from inference

This step is where most theories go wrong. A game may show a character walking into a room. It does not state that the character is alive, dead or something else. The first part is fact, and the second part is inference.

Write two lists side by side. On the left, put what the game directly shows or says. On the right, put what you think it means. Keep the two lists apart as long as you can. This habit stops a guess from hardening into a fact.

Be careful with voice lines and notes. A character can lie, misremember or speak in metaphor. The game states that the character said something, not that the statement is true. Treat every speaker as a possible unreliable source.

Community ideas spread fast and often lose their labels. A popular video may present a guess as settled fact. When you reuse that idea, check its source first. If you cannot find the original clue, mark it as unverified.

Use plain words for each claim. Say 'the poster shows a missing child' instead of 'the poster proves a kidnapping'. The second version adds meaning the game never gave you. Small wording choices keep a theory honest.

Finally, ask what else could explain the same clue. A torn poster might mean damage, age or a deliberate act. List the options before you pick one. The best theory survives more than one possible reading.

Step four: check, contradict and date your claim

Look for the developer's own statements before you publish. Interviews, patch notes and social posts can confirm or rule out an idea. Treat those statements as evidence with a date attached. A comment from 2021 may not apply to a 2024 chapter.

Then hunt for evidence that contradicts your theory. Search for clues that break it, not just clues that support it. If a single detail cannot fit, your theory needs a change. This step is uncomfortable but it is the most useful one.

Write the final claim so it can be tested. Instead of saying a character is secretly alive, say what evidence would prove it. A claim that cannot fail is not a theory. It is a belief that no clue can touch.

Date your theory and label it as a draft. New chapters, patches and sequels can change the facts. A dated draft lets other fans see how the story grew. It also protects you from being wrong forever.

Share your sources along with the claim. Link the chapter, the room and the exact clue. Other players can then check your work and add to it. That shared checking is what makes a community theory strong.

Update or retire the theory when new evidence arrives. A good theorist changes their mind when the facts change. That habit earns trust and keeps the discussion useful. It also keeps the fun alive for everyone.

Method in numbers

Theory steps

4

Collect evidence, note location, separate fact from inference, then check and date.

Minimum clues before a claim

2 or 3

One odd detail is usually too weak to support a theory on its own.

Typical first-run length

30 to 90 minutes

A short chapter gives you time to replay and recheck clues.

Genre age by 2024

10 years

A decade of chapters means old developer statements may be outdated.

Questions readers ask

How many clues do I need before I post a theory?

Two or three related clues are a good minimum. A single odd detail is often a joke, a bug or a red herring.

Can a developer statement settle a theory?

It can help a lot, but check the date. A comment from an early chapter may not apply to a later release or a sequel.

What if new evidence breaks my theory?

Change the theory or retire it. Updating your claim when facts change is normal. It also makes your next theory stronger.

From claim to checkable claimA funnel that narrows a broad community claim into one falsifiable statement.community claimevidence you found yourselfone testable statementKeep what survives the check; drop the rest.
A theory is worth posting when it has narrowed to something a later chapter could contradict.