WOBBLE - the subreddit's shared tower

One shared, irreversible tower per subreddit: every storey carries a redditor's name, every wobble is community history - and when it falls, the game itself posts the memorial, naming who toppled it.

Comment

Inspiration

Reddit is at its best when a whole community rallies around one fragile, shared thing. We wanted that feeling - but with skill and stakes. So WOBBLE gives every subreddit a single leaning tower that everyone builds together, one storey at a time, and turns its inevitable collapse into a public event that names the person who caused it.

What it does

There is one persistent tower per subreddit. Tap BUILD and a storey slides across the top - tap again to drop it. Land it centered and the tower stays steady; miss and it tilts. A lean bar shows how close the community is to disaster, and the taller the tower, the less it forgives. Land your storey and your name is carved on it for as long as the tower stands. Topple it, and the whole thing comes down for everyone - the game auto-posts a memorial ("Tower #14 fell at storey 87 - toppled by u/you") listing its top builders, and a fresh tower begins. Bricks regrow one every 3 hours (max 3), so you come back through the day; Practice mode is always free. Only one person builds at a time - everyone else watches the drop live, and a "you're next" queue keeps it fair. Recognition runs deep: every memorial ranks the fallen tower's top builders and calls out the most perfect drops and the single best save, and the game tracks your all-time record - storeys placed, towers survived, and towers you've toppled. (Subreddit flair badges are next on the roadmap.)

How we built it

Reddit's Developer Platform (Devvit Web) with an Express server and Redis. The shared tower is one canonical record; turns are handled by an atomic Redis SET-NX lock with a random token, so two simultaneous builders can never double-commit. The key trick: the tower's tilt is a single deterministic number (not a physics engine), so every device agrees on the exact state and the exact culprit - real physics is used only for the cosmetic collapse animation, which is recorded once and replayed. The server clamps every drop, which enforces two invariants at once: anti-cheat and anti-grief (no single bad storey can ever topple a fresh tower - proven by unit tests across 500 heights). Memorials are posted by the app account, and unit tests cover the tilt math and the game core.

Challenges we ran into

  • Keeping "one shared tower" consistent across many simultaneous players without a physics-sync nightmare - solved with a turn-lock, a scalar source of truth, and client-side replay.
  • Tuning the collapse cadence so towers fall roughly every 60–120 storeys for a mixed-skill crowd - found the right knob with a bot simulation.
  • Guaranteeing no lone griefer can knock down the community's tower, while two sloppy builders on a tall one still can.
  • A tap-only, sub-second, mobile-first webview inside a Reddit post.

What we learned

Designing a communal-object game where failure becomes the best content; using Devvit's atomic Redis primitives for fair turn-taking; and balancing a system that is forgiving of one honest mistake but brutal to carelessness.

What's next

  • A full all-time leaderboard - top builders, longest-standing towers, and the most (and least) destructive players - plus deeper per-tower stats; real Reddit flair ranks for master builders; tower themes beyond the default Leaning-Tower-of-Pisa look; and shareable memorial cards.

  • Tower Wars - subreddit vs subreddit seasons (each community already has its own tower; let them race), a global hall of fame for the tallest standing tower, and flair badges for legendary saves.

Built With

Share this project:

Updates

Submission history