The Button Game Stats
By Regen2Moon (K3N), Inspired by Josh Wardle.
Loading game data...
Error
Failed to load game data. Please try again later.
Game List
The Button Game
Hello! My name is K3N, and I would like to tell you about a community game bot called "The Button" that I created.
It's basically like playing "keep the balloon up"/"hot potato"/"don't let the bomb explode" but in Discord.
Everyone works together to keep a timer from hitting zero by clicking, so when someone clicks, it resets for everyone. The closer to zero the button gets, the rarer the color it changes to. So a user might be waiting to grab a specific color, and someone swoops in and "steals" it from them. I've seen some cool user interaction with this!
A user obtaining the rarest color! People were very excited.
The button game shown on Discord's mobile app.
Global Statistics
Technical Overview
TL;DR
The Button is a Discord bot implementing a continuous community game where users collectively prevent a timer from reaching zero. It uses a MySQL database for persistence, handles concurrent interactions through connection pooling, and implements a sophisticated color-based ranking system that rewards risky timing-based gameplay.
Architecture Overview
The system implements a distributed real-time interactive game environment utilizing:
- Asynchronous event handling through Discord.py's event loop
- Connection pooling for database concurrency management
- Sophisticated state management with atomic operations
- Multi-layered caching system for performance optimization
Core Mechanics
The fundamental game loop operates on several key principles:
- Timer Mechanics: Implements a continuous countdown system with configurable duration (default: 43200 seconds)
- Color States: Utilizes six distinct states based on remaining time percentage:
- Purple (83.33-100%): Lowest risk, lowest reward
- Blue (66.67-83.32%): Low risk
- Green (50.00-66.66%): Moderate risk
- Yellow (33.33-49.99%): High risk
- Orange (16.67-33.32%): Very high risk
- Red (0-16.66%): Maximum risk, maximum reward
- Concurrency Control: Implements mutex locking for critical sections and connection pooling for database operations
Technical Implementation Notes
Key technical considerations include:
- Race Condition Handling: Utilizes database transactions and row-level locking
- Cache Management: Implements multi-layer caching with TTL for game state and user data
- Error Recovery: Automatic reconnection and state recovery mechanisms
- Performance Optimization: Batch operations and connection pooling
Security & Privacy Notice
The bot requires minimal permissions: managing color roles and message management in designated channels. All role management is confined to game-specific roles at the bottom of the server hierarchy.
Required channels:
- Button channel: Displays game state and controls
- Chat channel: Activity notifications and community interaction