One More Thing

Inspiration

Most multiplayer games require everyone to be online at the same time. Reddit works differently: people arrive throughout the day, contribute something small, and leave behind content for others.

That inspired One More Thing, a daily community physics game where every player inherits the structure created by previous Redditors and adds one more object to it.

The idea is simple:

Your object becomes the next player’s problem.

What it does

Every day, the community receives one shared unstable tower.

Each player gets three object choices: Safe, Risky, and Absurd. They choose one, position it, rotate it, and drop it onto the existing structure.

If the tower remains stable, the object becomes a permanent part of the daily tower. Every player who arrives afterward must build on top of everything placed before them.

If the structure collapses, the failure is shown through an entertaining physics sequence, but the last stable community tower is restored so one player cannot destroy everyone’s progress.

Players can return later to see:

Whether their object is still standing
How many objects were added after theirs
How high the community tower has grown
Which milestones were reached
Who completed the most impressive placements

The hook

One More Thing is not only a stacking game. It is an asynchronous community-created challenge.

Every successful player changes the level for the next player. The tower becomes more difficult, strange, and personal as the day continues.

The main reason to return is curiosity:

Did the tower survive, and what did the community build above my object?

A new tower and physics modifier create a fresh challenge each day.

How we built it

One More Thing is being built as a Reddit Interactive Post using Devvit Web, Phaser 3, and Matter Physics.

Phaser powers:

Object movement and rotation
Collision and gravity simulation
Stability detection
Collapse sequences
Camera movement and screen shake
Particles, animation, and sound feedback
Responsive desktop and mobile controls

The Devvit server manages:

Reddit user identity
Daily player attempts
Object choices
Shared tower state
Persistent contributions
Tower version conflicts
Player statistics and leaderboards

Devvit Redis stores the accepted tower and reconstructs it whenever another player opens the post.

User contributions

Every accepted object is a meaningful player contribution.

It permanently changes:

The shape of the daily tower
Its balance and available space
The challenge inherited by future players
The community’s final result

Players are therefore creating part of the game for one another instead of only submitting a score.

Retention mechanics

The game is designed around natural community anticipation rather than repetitive rewards.

Retention features include:

One evolving shared tower each day
A daily ending countdown
Personal object ownership
Community milestones
Builder streaks
Daily physics modifiers
Final tower results
Recognition for notable placements

Challenges

The biggest challenge is keeping an asynchronous physics game fair and reliable.

Multiple players may begin placing objects from the same tower state. To prevent newer contributions from being overwritten, the game uses tower versioning and conflict-safe retries.

Another challenge is determining whether the complete structure is genuinely stable. The game evaluates movement across all tower objects rather than checking only whether the newest object touched the stack.

The controls also need to remain precise and enjoyable on both desktop and mobile inside a Reddit post.

What we learned

We learned that community participation becomes more meaningful when every small action creates a visible consequence for another person.

We also learned that failure does not need to feel like lost progress. A dramatic collapse can become part of the entertainment while the accepted community state remains protected.