> For the complete documentation index, see [llms.txt](https://assetstore.essentialkit.voxelbusters.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://assetstore.essentialkit.voxelbusters.com/features/media-services/playmaker.md).

# PlayMaker

Capture media from camera, select from gallery, and save images to the device gallery.

## Actions (12)

* Permission status (sync): `MediaServicesGetCameraAccessStatus`, `MediaServicesGetGalleryAccessStatus`
* Capture (async): `MediaServicesCaptureContent`, `MediaServicesGetCaptureContentError`
* Select (async): `MediaServicesSelectContent`, `MediaServicesGetSelectContentSuccessResult`, `MediaServicesGetSelectContentError`
* Save (async): `MediaServicesSaveContent`, `MediaServicesGetSaveContentError`
* Content converters (async; run in their own state and use `FINISHED`):
  * `MediaServicesGetContentTexture` (images → Texture2D)
  * `MediaServicesGetContentFilePath` (temp file path)
  * `MediaServicesGetContentRawMediaData` (bytes + MIME type)

## Key patterns

* **Permission checks are status-only**: the access status actions do not fire events. Branch using Enum Compare/Switch on the returned `status`.
* **Trigger actions fire events**: `CaptureContent`, `SelectContent`, `SaveContent` fire `successEvent` / `failureEvent`.
* **Converter actions have no success/failure events**: they finish when the async conversion completes (or log an error). Put them alone in a state and transition on `FINISHED`.
* **Cached content index**: after SUCCESS, use `contentIndex = 0..contentCount-1`. Converters fall back to the last captured content when no selection is cached.

## Use cases

Start here: `use-cases/README.md`


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://assetstore.essentialkit.voxelbusters.com/features/media-services/playmaker.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.