The metadata is written to a cache that is allocated and managed for your app by the system. Metadata can represent an 'event' which occurs at a single moment, such as when the user finishes a lap in a racing game, or it can represent a 'state' that persists over a span of time, such as the current game map the user is playing in. This can include text or numeric values, with a text label identifying each data item. The namespace provides APIs for creating metadata that describes the gameplay being captured or broadcast. The middle sections of this article walk you through the implemenation of these scenarios.

Both of these techniques produce an video file that can be accessed by your app, and depending on where you choose to save the files, by the user. If the user has enabled historical capture, then you can also record gameplay that has already occured by specifying a start time in the past and a duration to record. If capturing is enabled on the device, your app can start capturing gameplay and then, after some time has passed, you can stop the capture, at which point the media is written to a file. The other way to capture media is to use the APIs of the namespace. The first sections of this article will show you how to enable and disable system-implemented app capture and how to receive notifications when app capture starts or stops. Media that is captured using this technique is ingested into the Microsoft gaming ecosystem, can be viewed and shared through first-party experiences such as the Xbox app, and is not directly availble to your app or to users. The user can initiate capture using the built-in system UI. There are two different ways that gameplay can be captured in a UWP app. This article describes how to capture game video, audio, and screenshots, and how to submit metadata that the system will embed in captured and broadcast media, allowing your app and others to create dynamic experiences that are synchronized to gameplay events.

Bonetown pc game screenshot