gameface-drivinglisted

# Driving a Gameface UI This skill records the procedure for the `game_*` tools: the facts the tool schemas cannot tell you. Facts that may be game-specific are labeled; the reference target is Cities: Skylines II (CS2, Cohtml 1.64.0.7). For what the engine itself supports (layout, events, missing platform APIs), load the `gameface` skill; this one stays operational. ## Session start and triage Screenshot first and orient before acting: menus, dialogs, or a loading screen change what is safe to click. A capture holds the UI view alone: the application's own rendering never reaches it, and every transparent region comes back flat white, so an expanse of white is the normal backdrop of a HUD rather than a blank or broken UI. Read the application's state from what its UI displays, never from the scene behind it. When any tool fails, run `game_status` before retrying; it settles whether the endpoint is reachable and which engine and page answered. Read the page identity from `target.url` (for example `assetdb://gameui/index.html`). A dead endpoint mid-session usually means the game crashed or was closed. Report it and wait for the developer to relaunch the game; retry-looping cannot help, and testing that was interrupted mid-action may have left the UI in a state worth re-checking with a screenshot once the game is back. No reconnect ritual exists or is needed: the server re-resolves the page target on the next call after the game returns. ## Finding elements `game_query` is