Your Game Brief

Roflow keeps a short brief for each game. It describes what the game is and how it plays, and Roflow uses it to decide what to build and what to check. Open Progress in the chat header to see it.

What the brief holds

• The idea: what you asked for, in your words.
• The core loop: spawn, interact, feedback, progress, success, failure and replay.
• Devices (desktop, mobile, console, VR), players (how many), controls and style.
• Success and failure: what the game must achieve, and what would count as broken.
• Persistence: whether progress lasts only while playing, or should survive leaving and rejoining.

Where it comes from

• A new game starts from your first request. Anything you did not say gets a sensible default, and the brief lists those under Defaults stated so you can see what Roflow assumed.
• A game you already had is read from the place itself: the first time Roflow changes it, it describes the game as it plays now, and lists those fields as Read from your game. See Games You Already Have.
• You can change any of it by saying so in the chat ("this is a two-player game", "it should save progress"). What you set always wins over defaults and over what Roflow read.

Questions Roflow asks

Some details change how Roflow builds, such as whether progress should save. When the brief cannot tell, Roflow lists the question under the brief and may ask you in the chat.

Requirements

The brief turns into a list of requirements, each tied to a part of the core loop. Every play-test updates them: passed, failed, or still waiting for evidence.