5 Roll Project Report
1. The Concept
5 Roll is a mobile-first, Yahtzee-style dice web game designed for quick and accessible casual play. Players roll five dice, hold useful results, and roll again up to three times per turn. They then choose a scoring category and try to complete the entire score board with the highest possible total.
The project began as a simple random dice roller. During planning, the concept was expanded into a complete game with meaningful player decisions, risk and reward, score combinations, multipliers, and replay value. The final concept remains easy for beginners to understand while offering enough strategy for experienced players.
2. The Stack
The Stack: HTML5, CSS3, and vanilla JavaScript form the core of the application. Browser localStorage preserves the best score, selected language, and sound preference. Python scripts support the creation and processing of visual assets. The project runs as a static web application and uses no framework, database, account system, or backend server.
The AI Assist: AI helped define the target audience, refine the gameplay concept, review the project against game-design and UI/UX rules, create English and Khmer interface text, develop the scoring system, generate visual assets, test browser interactions, identify design problems, and prepare project documentation.
3. The 1 Day Sprint
Morning (Hours 1–3): The first stage focused on research and planning. Game-design references were reviewed to identify the core requirements: immediate clarity, simple controls, meaningful choices, fast retry, strong feedback, and replay value. The target audience was defined as casual mobile players who enjoy short games. The original dice-roller idea was then developed into a structured five-dice scoring game.
The project structure was prepared with separate files for gameplay, interface text, audio, styling, visual assets, and supporting scripts. The basic game states—home, play, help, and results—were also established.
Afternoon (Hours 4–6): The main gameplay system was implemented. Players could roll five dice, hold selected dice, reroll the remaining dice, preview available scores, and record a result in one of thirteen categories. Three multiplier columns were added to create 39 scoring opportunities and give the player more strategic choices.
The interface was designed for a portrait, mobile-first experience. English and Khmer localization, sound controls, undo behavior, responsive layouts, score tracking, and browser-based preference storage were added. Game-specific image assets were used for backgrounds, buttons, panels, and dice.
The Finish Line (Hours 7–8): The final stage focused on integration, testing, and refinement. The roll, hold, score, undo, language, sound, and result flows were checked in the browser. Unnecessary complexity and unused visual elements were reviewed, interface wording was shortened, and the documentation was updated to match the implemented game.
The completed build included a playable scoring loop, bilingual support, responsive presentation, persistent best scores, help instructions, and a replayable finish screen.
4. The Roadblocks
Roadblocks: The largest challenge was finding gameplay that felt appropriate for a simple dice game. A purely random dice roller had little player agency and became repetitive quickly. An early target-matching approach introduced more decision-making, but it required too much calculation for the intended casual experience. The design was therefore revised into a familiar five-dice scoring system with holds, rerolls, and selectable score categories.
Another challenge was balancing a bilingual interface. Khmer text can require different spacing and width from English, so button labels and instructions had to remain short and responsive. The project also needed to feel like a mobile game rather than a conventional website. This required full-screen layouts, large tap targets, limited text, clear visual hierarchy, and dedicated image assets.
Visual-asset preparation also required several iterations. Background removal, dice consistency, button readability, and unused-file checks were necessary to keep the final interface coherent and the project directory organized.
5. Key Takeaways
A simple concept still needs meaningful decisions. Random results create surprise, but holding dice, choosing when to reroll, and selecting a score are what turn that randomness into gameplay.
Clear UI is part of the game mechanic. Players must understand the current dice, remaining rolls, available scores, and next action within a few seconds.
Mobile-first design requires more than making a desktop page smaller. The interface must prioritize touch controls, readable text, full-screen composition, and one clear action at a time.
Separating gameplay logic, localized text, audio, styling, and assets makes the project easier to test and improve. Browser storage also provides useful progress without requiring a backend.
My final thought: 5 Roll demonstrates how a small luck-based idea can become a complete and replayable game through clear player choices, focused UI/UX, and careful iteration. The one-day sprint produced a solid foundation that can be expanded later with improved balancing, additional game modes, achievements, and optional online competition.