Don’t Press the Button

Don’t Press the Button was an original Roblox UGC game concept that I designed and scripted independently.

Players entered a shared map with one simple instruction: do not press the button. A server-wide timer counted down from 30 minutes. If anyone pressed the button, the timer reset for everybody.

Players who remained until the countdown completed earned a UGC Ticket, which could then be spent in the game’s UGC shop.

The game reached approximately 12,000 visits and generated thousands of Robux while it was publicly available.

The project was valuable because I owned both the concept and its implementation. I was not handed a predefined gameplay loop; I designed the social tension, progression structure, reward currency, and shop around the central button mechanic.

• -Approximately 12,000 visits
• -Thousands of Robux generated
• -Original game concept
• -End-to-end gameplay scripting
• -UGC-focused reward economy

The core mechanic depended on shared consequences. One player could undo the progress of the entire server, which created tension, cooperation, frustration, and social interaction without requiring a complicated control scheme.

The simplicity was intentional. Players immediately understood the objective, while the shared timer created unpredictable situations based on the behavior of everyone else in the server.

The countdown was controlled entirely by the server. Clients displayed the remaining time, but they could not decide when the timer started, when it reset, or whether a player had completed the challenge.

This was important because the reward had value. A client-controlled timer would allow exploiters to skip the waiting period or grant themselves tickets without completing the challenge.

• -One authoritative timer shared by the server
• -Server-controlled reset when the button was pressed
• -Consistent countdown replication to every player
• -Server-side winner and eligibility checks
• -No client authority over reward completion

The button was more than a physical object in the map. Its state needed to remain synchronized so that every player saw the same reset and the countdown returned cleanly to 30 minutes.

Interaction handling also required debouncing so one activation could not trigger a large number of duplicate resets.

Completing the countdown awarded the player a UGC Ticket. Tickets acted as the progression currency for the dedicated UGC shop.

Ticket balances and purchases were handled through server-side logic so players could not grant themselves rewards, reuse the same ticket, or submit fake shop values from the client.

• -Server-authoritative UGC Ticket rewards
• -Persistent ticket balances
• -UGC shop purchase validation
• -Eligibility checks before rewards were granted
• -Protection against repeated claims and fake purchases

The strongest part of the concept was the conflict between individual choice and group progress. Every player benefited from waiting, but any player could reset the challenge at any moment.

That structure naturally encouraged players to communicate, warn each other, guard the button, or deliberately disrupt the server. The social interaction came directly from the mechanic rather than from scripted dialogue or complex content.

I handled the project from concept through implementation, including the shared countdown, button behavior, reward distribution, ticket persistence, and UGC shop.

• -Original gameplay concept and loop
• -Server-wide countdown system
• -Button interaction and reset handling
• -UGC Ticket reward system
• -Persistent player currency
• -UGC shop and purchase validation
• -Live deployment and monetization

The original experience has since been made private, so there is no public game link or YouTube demonstration available.

While active, the game reached around 12,000 visits and generated thousands of Robux. It remains an example of my ability to take a simple original idea and develop it into a complete, monetized Roblox experience.