> For the complete documentation index, see [llms.txt](https://docs.drizz.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drizz.dev/running-tests/game-mode.md).

# Game mode

Game mode runs Drizz from the rendered screen alone, ignoring the view hierarchy.

|                     |                                                                |
| ------------------- | -------------------------------------------------------------- |
| **Platforms**       | Android · iOS                                                  |
| **What it changes** | Drizz works from the screen alone, ignoring the view hierarchy |
| **Who turns it on** | Drizz, per app — not self-serve                                |
| **How to get it**   | Ask your Drizz contact                                         |

## Prerequisites

* A package or bundle ID to enable it against
* A Drizz contact — there is no self-serve setting

## What it applies to

A normal app exposes a view hierarchy Drizz reads alongside the screenshot. A game rendered on a canvas or in an engine exposes one large surface with nothing named inside it. Game mode drops the hierarchy and works from the rendered screen.

It applies to games, and to any app with a screen that renders as a single canvas — a map, a chart surface, or an embedded engine — where normal targeting fails on that screen.

## Get it enabled

1. Identify the package or bundle ID.
2. Ask your Drizz contact to enable game mode for it.
3. Run a test against the affected screen and confirm targeting resolves.

## Common mistakes

| What you do                                            | What happens                                                                                |
| ------------------------------------------------------ | ------------------------------------------------------------------------------------------- |
| Look for a game mode toggle in the app                 | There isn't one. It's enabled per app by Drizz                                              |
| Assume normal command behavior carries over unchanged  | Unconfirmed. Confirm scope before writing the suite                                         |
| Request game mode because one screen is hard to target | Exact wording and neighbor context resolve most of these — see [Tap](/writing-tests/tap.md) |

## Next

* [MAP\_ACTION](/writing-tests/tap/map-action.md)
* [Devices](/running-tests/devices.md)
* [Known limitations](/reference/known-limitations.md)

***

*Last updated: 6 August 2026*