Horror Thursday — Tower of Knocks

The trigger

Two signals line up well here. First, there is explicit player demand for horror that does not rely on first- or third-person camera work because of motion sickness. Second, GameDiscoverCo's note about Steam games with CCU staying power points toward loops that create repeatable nightly tension instead of one-and-done scripted scares. Add today's Brazil industry story, and there is also a timely production angle: a compact horror game rooted in apartment-block folklore can feel culturally specific without requiring open-world scope.

The idea

A side-on dollhouse survival horror set in a cursed apartment tower. By day, you move through a single vertical building, learning each tenant's habits, grudges, hiding places, and practical needs while scavenging tape, salt, candles, locks, and gossip. By night, the building changes rules: something roams the halls, doors knock on their own, and residents panic, wander, lie, or freeze. The game is about routing vulnerable people room to room, sealing corridors, deciding who gets the good protections, and surviving until dawn with as many tenants intact as possible. The horror comes from attachment, incomplete information, and hearing disaster move one wall closer.

The core loop

Day phase: talk to tenants, note routines, trade favors, inspect apartments, gather limited supplies, and discover which protections work on which floors. Night phase: watch the tower cross-section, respond to knocks and power failures, issue simple commands to residents, barricade doors, relocate people, burn scarce wards, and accept that you cannot save everyone. Dawn phase: count losses, unlock new rumors, upgrade your knowledge of the entity's rules, and prepare for the next night.

Why now

This answers a clear unmet ask: horror for players who cannot handle common POV conventions. It also borrows a proven retention shape from games people cite after Dredge: short expeditions, return-to-safety relief, light logistics, and escalating dread. The apartment-block format supports strong worldbuilding and NPC attachment in a tiny playspace, which matters because players asking for richer worlds often really want memorable inhabitants, not literal map size. A folklore-forward setting also gives you a differentiation hook that is easier to localize than heavy text adventure design, fitting today's broader discussion around global audiences.

Scope

First playable milestone: one five-floor building, six named tenants, one entity, three protection types, and a three-night campaign. The entire game can ship at small-commercial scope with one building tileset, mostly UI-driven interaction, limited animation, and systemic audio cues instead of cinematic scenes. If the prototype works, expand to 8-10 tenants, 7-10 nights, a handful of tenant event chains, and two or three late-game rule twists. Do not add free-roam city exploration, combat, or elaborate branching dialogue trees.

What kills it

If tenant behavior is not readable, the whole game dies. The pitch depends on players learning habits, forming favorites, and making informed triage decisions under pressure. If residents feel random or stupid, this collapses into a frustrating door-clicking toy and players will bounce to games that already own civilian-management dread, like This War of Mine, or to more direct survival horror. The other scope trap is writing too much dialogue for too many residents.

Prototype one night cycle first. If moving one scared tenant across two hostile hallways is not tense in graybox, do not build the full tower.