A useful bug report needs more than a still image. The recorder was integrated into the game’s testing flow so a clip could show movement, the HUD and the DOM pause screen together. It captures the direct stereo game mix and does not request a microphone.
Browser sharing still needs the player’s initial approval. Once a game-tab capture session is connected, the recorder can be started and stopped from the visible controls or its controller shortcut. The local setup also includes a private conversion helper for producing MP4 output when the browser’s capture format needs conversion.
Verify the file, not only the button
One saved gameplay acceptance clip ran for just over 65 seconds and was inspected as a genuine H.264/AAC MP4: 2134 × 1200 pixels at 30 frames per second, with stereo 48 kHz audio. That check established what the local recording path actually produced, rather than relying on a filename extension.
Recorder routing is kept separate from ordinary game inputs. Sharing permission, recording, pausing and returning to the game each need to release or preserve the right controls. The later controller-recovery work tightened this boundary further. At this milestone, website clip publishing remained disabled and no clip was published to a website by the recorder.