Start with a verifiable core loop
A useful creator request is not a feature pile. It names a loop a player can experience, then lets theme, difficulty, and visuals support that loop.
- State the round length, survival goal, and reward before naming disasters.
- Give spectators, late joiners, and eliminated players explicit states.
- Test wins and coins as server decisions, never as client claims.
Check the edge cases, not just the disaster
Write down the state sequence: lobby, intermission, active round, result, return to lobby. Then decide what a late joiner sees, whether eliminated players can re-enter, and when rewards are granted. Test one-player behavior first; a separate two-player Studio run is needed to verify shared round state and independent rewards. A structural Build check is not evidence that actual players experienced a fair round.
Copyable survival prompt
Create a toy-city Roblox Round Survival Draft. Players enter from a lobby, see a countdown, survive one announced hazard per round, and return to the lobby after results. The server decides eliminations and survivor rewards. Include a readable HUD and show me the plan before building.