Dead Circuit

Inspiration

Dead Circuit started with a simple question: what would tower defense feel like if the player was not safely above the battlefield?

Most tower defense games let the player place defenses, watch enemies approach, and optimize from a distance. I wanted to invert that fantasy. In Dead Circuit, the towers are still the weapons — but the player is inside the failing facility, responsible for keeping those weapons alive. The inspiration came from combining tower-defense strategy with maintenance-horror tension: no guns, no direct combat, just power routing, damaged systems, and the terrifying decision to leave safety and repair something before the line breaks.

The core hook became:

Every repair is a risk.

What I Learned

This project reinforced that a strong game concept is not just a theme mashup. “Tower defense plus horror” is not enough by itself. The horror has to change the mechanics.

The strongest version of the idea emerged when repair became the center of the game:

• Repairing narrows your camera view.
• Repairing creates noise.
• Some enemies follow noise.
• Power is limited.
• Towers are powerful, but fragile.
• The player cannot fight directly.

I also learned that scope discipline is part of the design. A bigger idea is not always a better idea. The most competitive version of Dead Circuit is not a giant stealth-horror campaign. It is a focused, mobile-first co-op tower-defense prototype built around one unforgettable moment: fixing a tower while something is coming.

How I Built the Project

I developed Dead Circuit as a pre-production design package focused on four core deliverables:

1. Game Design Document — defined the core loop, target player, systems, progression, and feasibility.
2. Player Journey Map — mapped the first 15 minutes around a fast hook, system onboarding, tension curve, and “one more run” ending.
3. Production Plan — scoped the smallest honest version of the game and sequenced development around validating the core repair-under-threat loop first.
4. Visual Concept Package — established the emergency-lit horror style, UI language, field view, control room, enemy silhouettes, and repair-risk moment.

The concept was built through iterative review and refinement. I used AI assistance to pressure-test the idea, compare it against existing games, identify scope risks, strengthen the contest fit, and revise the deliverables for clarity and competitiveness. Human judgment guided the final decisions: what to keep, what to cut, and how to preserve the core promise.

Challenges

The biggest challenge was avoiding familiar territory. First-person tower defense exists, and horror tower defense exists. The design needed a stronger differentiator than camera angle or scary enemies.

The solution was to remove direct combat entirely.

That decision clarified everything. The player is not a shooter. The player is a technician. The towers fight. The player keeps them alive.

Another challenge was balancing ambition with feasibility. Co-op, horror, mobile-first play, tower defense, repair mechanics, power routing, and enemy detection could easily become too complex. The production plan solves this by focusing the MVP on a tight first playable:

• One facility sector
• Three defensive systems
• Three enemy types
• Three repair interactions
• One power grid
• One breach event
• One core proof: repairing the defense is more dangerous than placing it

What Makes It Different

Dead Circuit changes tower defense by putting the player inside the machine.

The strategic question is not only:

Where should I place defenses?

It is:

Can I survive long enough to keep them working?

That shift turns maintenance into strategy, repair into horror, and tower defense into a tense co-op systems-management experience.

What's next for Dead Circuit

TBD! Let's dream!

Built With

• chatgpt
• claude
• word