Share or steal, a Roblox game in the making
One vote, fifteen seconds, and trust put to the test.
Project at a glance
- The need
- Create a game of trust and betrayal in which each player’s choice decides the round.
- My contribution
- Wrote the game code in Luau: round loop, progression, persistence and interface. Systems still to be connected are detailed in the case study.
What was built
- Server and client code
- Round loop
- Progression
- Code diagrams
Paused, unpublished project. Code reviewed, not executed for this case study, with no automated tests; the visuals are diagrams, not game screenshots.
- Nature
- Roblox game · personal project in progress, unpublished
- Period
- Since January 2026
- Client
- Projet personnelPersonal project, unpublished
The project
A Roblox game written in Luau, in the making and not yet published. The idea comes down to one question: each round, every player has fifteen seconds to choose to share or to steal. If nobody steals, everyone wins. If a single player steals, they win and those who shared are eliminated. If several steal, they are the ones eliminated.
What the code contains
- The server’s game loop: waiting for players, an optional event out of seven, vote, verdict, reset.
- A shop of titles and boosters bought with the in-game currency, a win-streak bonus and level-based progression.
- Twelve achievements and seven random events.
- Saving of progress in a Roblox data store, with a backup copy: when the player leaves, when the server shuts down and every three minutes.
- A reporting system (four reasons, one minute between two reports, automatic kick after three reports within five minutes) and an anti-cheat check on the vote: one vote per round.
- An interface written as a single client script of about three thousand lines, and camera effects.
Evidence
Every figure carries its source. No commercial result is claimed.
6 204
Lines of Luau (comments and blank lines included)
SourceCount of the project folder’s 16 files, 3 October 2026
7
Random events in the code
SourceThe game’s events module, 3 October 2026
12
Achievements defined in the code
SourceThe game’s achievements module, 3 October 2026
Where the project stands
The game is not published and has no screenshot to show: this file’s two visuals are diagrams composed from the code, not images of the game. The project has been on pause since February 2026, and I intend to finish it. Several systems are written but still have to be wired in: some of the events, boosters and anti-cheat checks, and the achievements' badges.
What is not claimed
No player, no live match, no sale and no revenue: there is no result to claim. The figures in this file measure code written, not success. The code was read for this file, not run, and it has no automated tests. No graphic or sound asset from the game is shown here.
Technical details
The technologies used for this project. Features and their limits are detailed in the narrative.
- Luau
- Roblox
- Rojo
Gallery
How a round plays out, from the code (a diagram, not a screenshot). 
Where the code lives, folder by folder.
A similar need?
Let's discuss your context and what you would like to simplify.