game-recon

1# Game recon
2 
3Goal: in about five minutes, know what you're dealing with and which route to take. Write the answer down
4so every later step can rely on it.
5 
6## 0. Has another agent been here?
7`um kb search "<game>"` (and the engine name). A field note in the shared knowledge base can hand you the
8working versions, the route, and the gotchas before you touch anything. See the **share-field-notes** skill.
9 
10## 1. Find it and fingerprint it
11```bash
12um scan --list                 # Steam, Epic and Xbox installs (Windows, WSL, Linux, macOS)
13um scan "<name or folder>"     # host, engine, version, exes (.NET?), anti-cheat, loaders,
14                               # mod folders, saves, routes
15um scan "<game>" --json        # the same, machine-readable
16```
17`um` lives at `bin/um` in the universal-modder repo (plugins and clones put it on PATH). Anywhere else:
18`uv tool install git+https://github.com/rehan-remade/universal-modder`.
19 
20`um scan` reads files only. It indexes the install (bounded), sniffs PE headers, the Unity/Godot/GameMaker
21headers and the Unreal version string, maps known games to their community loader, and points to the
22playbook to read: `skills/mod-any-game/references/engines/<engine>.md`.
23 
24The scan can't see everything, so check these by hand:
25- **Game not in a store library** (GOG, itch, a standalone folder): pass the folder path.
26- **Several engines' signals:** launchers and web helpers are common. The top score wins, but read the
27  "also" line.
28…