Goblin Sneeze Factory

Why it might work

• ↑The path-network topology produces a workshop layout that is structurally different for every player after round 5 — two players who both reached round 10 will have networks with different graph structures (edge counts, junction densities, sub-graph connectivity) based on which threads they chained through, making each run a distinct routing puzzle that cannot be solved with memorized solutions.
• ↑The tug counter auto-end at 0 means analysis paralysis has a concrete, visible cost: every second spent not tugging is a second closer to a goblin knotting its thread and severing a graph edge — the punishment is topological and permanent, not just a score penalty, and players can see exactly which edge they are about to lose.
• ↑A chain of 6 goblins resolving across a network with 3 junction pegs and 2 Weave Anchors produces a yarn-ball path with 5 direction changes in under 4 seconds — this is a 4-second clip with a clear start (one tug), visible cause-and-effect at each junction, and a payoff (chain counter hitting 6 and a Thread Reroute announcement). Capturable in a single screen recording with no editing.
• ↑The cozy cottage aesthetic (warm amber lighting, wool textures, knitting goblin animations, soft pop sounds on each junction) makes the same chain-reaction mechanic feel satisfying rather than chaotic — the visual language of yarn and thread naturally communicates the path-network topology to players who have never seen a graph data structure.

Why it might fail

• ↓Path-network topology is harder to read at a glance than a tile grid — players accustomed to grid-based games may not immediately understand that yarn-balls travel along thread edges rather than in straight lines, requiring a more explicit onboarding sequence than the original grid concept needed.
• ↓Thread Reroutes that change network topology mid-run can produce non-intuitive graph structures where a previously valid 3-goblin chain path no longer exists not because of a hazard tile but because an edge was literally redirected — players may attribute this to randomness rather than their own earlier chain choices, breaking the feedback loop.
• ↓Rendering a dynamic path-network graph with animated yarn-ball traversal, Tangle Knot accumulation states, Weave Anchor delay animations, and thread snap effects at 60fps on devices with less than 3GB RAM will require a dedicated low-fidelity render mode that replaces yarn textures with colored lines — without it, network resolution will drop frames at exactly the moment the visual payoff is supposed to land.
• ↓Players who identify that tugging a goblin on an isolated thread segment (one with no outgoing junctions) produces a guaranteed 1-goblin chain with no Tangle Knot risk can systematically play safe 1-goblin tugs every round, accumulating zero Thread Reroutes indefinitely — this requires a minimum reroute floor (e.g., 1 reroute per round regardless of chain length) to prevent the topology evolution system from being bypassed entirely.