Playtesting and verification
How RoGenie proves its work - static checks, scans, screenshots, playtests and playing your game like a real player - and how to turn runtime playtests off.
On this page
RoGenie does not stop at writing code. It checks that the code actually works in your place, and fixes what is broken before it tells you it is done.
What RoGenie checks
From cheapest to most thorough:
| Check | What it does |
|---|---|
| Validate | Fast static checks of scripts and targets in edit mode, such as syntax errors and API names that do not exist. |
| Geometry Scan | Finds hidden parts, z-fighting, duplicates and parts that intersect. |
| UI Layout Scan | Finds GUI elements cut off by the screen, overlapping each other, or sized so they will not scale on other devices. |
| Screenshots | Captures the Studio viewport so RoGenie can see what it built. Screenshots appear in the work log. |
| Playtest | Runs your game in a Studio playtest for runtime and physics proof, and reads the output. |
| Play as Player | Plays your game like a real player in a real Play session, with a live player, client and input, and reports what happened. |
| Runtime Eval | Reads or changes state inside the running game during a play session, for example a player's health or coins. |
| Profiler | Measures live FPS, frame time and memory. |
Playing your game like a real player
For gameplay, RoGenie can play the game itself: it moves the character, presses buttons, triggers prompts and touches parts, then checks the game state after every action. If something is wrong, for example an NPC's health did not change when it was hit, it repairs the code and replays until every check passes.
Tell RoGenie what "working" means in your wish to get the most out of this: "players should keep their coins after rejoining", "the door should only open for players with the key".
Playtest verification on or off
Playtests are the most thorough check, and the most expensive in tokens. You can turn runtime playtesting off in Settings › Agent › Playtest verification. With it off, RoGenie skips runtime playtests to save tokens; static checks (compile, validation and scans) still run.
You can also switch individual checks off for a session in Tool access, in the Verification group.
Imported games and reference folders
If your place contains scripts you imported only as reference, they can run during playtests and confuse the results. RoGenie's Reference Quarantine tool can disable the scripts under a reference folder, reversibly, so they stop polluting playtests.
Tips
- Keep Studio open on the place while RoGenie playtests, and avoid clicking around in Studio until the playtest finishes.
- If a playtest seems stuck, press Stop in the app, then stop the play session in Studio if it is still running.
- Playtests make model calls like any other step, so they use your quota.
- A screenshot RoGenie takes is real evidence: look at the ones in the work log to see what it saw.