Weird Wednesday — Input Cascade

The trigger
A post on /r/gamedesign explicitly asked for a game where one set of inputs controls a chain of characters across different nested games. That is a rare, direct player request for a mechanic, not just a theme. It also lands in a week of industry chatter about AI, decompilation, and ownership: a small, hand-authored interaction trick is a safer place for a solo dev to search for distinctiveness than trying to win on content volume.

The idea
Build a puzzle game where every input advances three tiny games at once. One screen might be a side-view platform room, one a top-down stealth grid, and one a falling-piece lane. Pressing Left affects all three layers according to their local rules; Jump might make the platformer hop, make the stealth avatar wait in place, and release a token in the sorter. The whole game is about finding a short shared input sequence that solves all three spaces on the same timeline. The hook is not reflex multitasking; it is planning around side effects.

The core loop
Read the three rooms, predict what one shared command will do in each layer, enter a short sequence of inputs, watch all layers resolve step by step, then rewind instantly and adjust. Success comes from discovering sequences where a move that looks wasteful in one layer is exactly what another layer needs. Minute to minute, the player is simulating consequences, testing, and refining a tiny script.

Why now
The demand signal is unusually clean: someone directly asked for this exact structure, and other community posts point to appetite for games with deliberate friction and strong mechanical identity, whether that is tank-control clunk or tightly coherent systems. There is also a broader problem of players saying they cannot get hooked anymore; a fresh control premise can earn attention fast without requiring hours of onboarding. For a solo dev, that matters more right now than chasing a crowded genre with expensive content expectations.

Scope
First playable milestone: 6 handcrafted puzzle rooms, 3 simultaneous layers, 4 shared inputs (Left, Right, Action/Jump, Wait), instant step rewind, and a timeline scrubber. Keep each layer extremely small: a 2D platform room with key + exit, a 5x5 stealth room with one patrol route, and a single-lane drop sorter with two target bins. No story, no procedural generation, no unlock meta, no more than one special rule per layer. If the prototype works, the gain comes from better room design, not more systems.

What kills it
Readability kills or saves this project. If players cannot reliably predict what an input will do across all three layers, they will brute-force sequences and the game stops feeling smart. The second killer is scope creep: a fourth layer, real-time pressure, or too many room-specific exceptions will turn a sharp experiment into an unreadable mess.

If you build it, spend day one on visualization and rewind, not content.