Main Street Chapter Guide

What does Main Street cover?

Main Street is the Town Center chapter in the sourced campaign matrix. Its six conditions involve Tanya’s Tier 3 Stalk, Rachel’s cemetery execution, the Slab scene, Eric’s hardware-shelf Stalk, Rachel’s friends, and an alert-free condition. Reward names remain unverified because the checked IGN chapter page is a stub. This page is organized around chapter context, challenge wording, and the route a player can actually verify. It gives the source-backed answer first, then separates adjacent claims so a player can check one result without treating an unlisted detail as confirmed.

The useful boundary here is practical: opening Town Center can be checked against iig, ign, official, thegamer, but no unsupported rate or timer is added.

How do Tanya and Eric differ?

If your question is about tanya, the published answer is specific: One condition fully stalks Tanya at the cash register to Tier 3. Into Indie Games is the source role attached to that row, so this page does not replace it with a fan-made estimate.

A useful check is to note the tanya alongside the map, chapter, role, store, or build where you saw it. Then stalking the named resident. If the prompt or result differs, preserve the observation and the date instead of silently upgrading it to a universal rule. This is a source-led answer, not a prediction. It gives you a way to stalking the named resident and tells you where the wording came from: iig, ign, official, thegamer.

When should you wait for the Slab scene?

A player can act on rachel and the slab without pretending the whole system is mapped. The checked wording is: The cemetery execution and Slab scene are separate conditions; the latter requires waiting rather than killing Rachel early. The next useful comparison is reward boundary, which has its own evidence trail.

A useful check is to note the rachel and the slab alongside the map, chapter, role, store, or build where you saw it. Then waiting for the scene. If the prompt or result differs, preserve the observation and the date instead of silently upgrading it to a universal rule. Keep the question tied to the evidence. To waiting for the scene, compare the in-game result with the published record from iig, ign, official, thegamer.

What is the cemetery condition?

Treat Reward boundary as the page’s working checkpoint. No chapter reward names are published here because the checked IGN chapter page is a stub. That is enough to checking the cemetery context; it is not evidence for an unlisted cooldown, spawn rule, reward, or score calculation.

A useful check is to note the reward boundary alongside the map, chapter, role, store, or build where you saw it. Then checking the cemetery context. If the prompt or result differs, preserve the observation and the date instead of silently upgrading it to a universal rule. The checked sources (iig, ign, official, thegamer) support the named checkpoint; they do not turn an unlisted mechanic into a confirmed rule.

A reproducible first check looks like this:

1. Open Town Center map and choose the named context before starting.
2. Use Reward boundary as the named checkpoint for the run.
3. Log what happened, when it happened, and how Town Center setting appeared.
4. Compare the result with the campaign hub before calling it a general rule.

Why are rewards withheld?

The answer changes depending on what you are checking. For town center setting, the cited record says Main Street is mapped to Haddonfield Town Center. Keep that beside the context for tanya before reporting a result.

A useful check is to note the town center setting alongside the map, chapter, role, store, or build where you saw it. Then avoiding an unsupported cosmetic claim. If the prompt or result differs, preserve the observation and the date instead of silently upgrading it to a universal rule. Read this as an updateable field guide: avoiding an unsupported cosmetic claim is actionable now, while anything outside the cited wording stays open.

How can a stealth clear be documented?

Start with Tanya. One condition fully stalks Tanya at the cash register to Tier 3. The related source is Into Indie Games. That distinction matters because rachel and the slab is a neighboring checkpoint, not an automatic consequence of the first one.

A useful check is to note the tanya alongside the map, chapter, role, store, or build where you saw it. Then recording alerts and chapter state. If the prompt or result differs, preserve the observation and the date instead of silently upgrading it to a universal rule. For recording alerts and chapter state, use the named fact as the checkpoint and the source list (iig, ign, official, thegamer) as the audit trail.

What should not be inferred from these sources?

The evidence set for this page is iig, ign, official, thegamer. It supports the rows above, but it does not publish every cooldown, spawn point, drop rate, score formula, cosmetic inventory, or farming route. Those omissions are deliberate. If a later official post or a reproducible in-game test adds one, update the row and its check date rather than backfilling the gap with a guess.

For the next step, open Town Center map and the campaign hub. Those links carry the reader to a neighboring question instead of ending the session at a definition.

Related checks for this question

Use the Stalk page when you need the wider campaign context, then return to Town Center map for the named checkpoint. the campaign hub provides the second angle: it helps you separate town center setting from tanya instead of combining them into one unsupported conclusion. The FAQ is a compact maintenance list; when a source changes, update the relevant row, wording, and last-modified date together.