Back to Details

game-recon

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Game recon

游戏侦察

Goal: in about five minutes, know what you're dealing with and which route to take. Write the answer down so every later step can rely on it.
目标：大约五分钟内了解需要处理的对象，并确定应采用的路线。将结论写下来，以便后续每一步都能以此为依据。

0. Has another agent been here?

0. 是否有其他 Agent 做过？

um kb search "<game>"
(and the engine name). A field note in the shared knowledge base can hand you the working versions, the route, and the gotchas before you touch anything. See the share-field-notes skill.
um kb search "<game>"
（以及引擎名称）。共享知识库中的现场笔记可以让你在开始操作之前了解可用版本、路线和注意事项。请参阅 share-field-notes skill。

1. Find it and fingerprint it

1. 查找游戏并识别其特征

bash
um scan --list                 # Steam, Epic and Xbox installs (Windows, WSL, Linux, macOS)
um scan "<name or folder>"     # engine, version, exes (.NET?), anti-cheat, loaders, mod folders, saves, routes
um scan "<game>" --json        # the same, machine-readable
um
lives at 
bin/um
in the universal-modder repo (plugins and clones put it on PATH). Anywhere else: 
uv tool install git+https://github.com/rehan-remade/universal-modder
.
um scan
reads files only. It indexes the install (bounded), sniffs PE headers, the Unity/Godot/GameMaker headers and the Unreal version string, maps known games to their community loader, and points to the playbook to read: 
skills/mod-any-game/references/engines/<engine>.md
.
The scan can't see everything, so check these by hand:
  • Game not in a store library (GOG, itch, a standalone folder): pass the folder path.
  • Several engines' signals: launchers and web helpers are common. The top score wins, but read the "also" line.
  • Anti-cheat installed elsewhere: kernel drivers (Vanguard's 
    vgk.sys
    ) and launcher-level protection don't live in the game folder. Search "<game> anti-cheat".
  • Online-only or live-service games: treat them as protected even if nothing was detected.
bash
um scan --list                 # Steam、Epic 和 Xbox 的安装项（Windows、WSL、Linux、macOS）
um scan "<name or folder>"     # 引擎、版本、exe（.NET？）、反作弊、加载器、mod 文件夹、存档、路线
um scan "<game>" --json        # 同上，机器可读格式
um
位于 universal-modder 仓库的 
bin/um
中（插件和克隆仓库会将其添加到 PATH）。在其他位置可使用： 
uv tool install git+https://github.com/rehan-remade/universal-modder
。
um scan
仅读取文件。它会对安装目录进行有界索引，嗅探 PE 头、Unity/Godot/GameMaker 头以及 Unreal 版本字符串，将已知游戏映射到对应的社区加载器，并指出应阅读的指南：
skills/mod-any-game/references/engines/<engine>.md
。
扫描无法发现所有信息，因此需要手动检查以下内容：
  • 游戏不在商店库中（GOG、itch 或独立文件夹）：传入文件夹路径。
  • 出现多个引擎的特征信号：启动器和 Web 辅助程序很常见。得分最高的结果会胜出，但也要阅读“also”一行。
  • 反作弊安装在其他位置：内核驱动（Vanguard 的 
    vgk.sys
    ）和启动器级别的保护并不位于游戏文件夹中。搜索“<game> anti-cheat”。
  • 仅支持在线或属于 live-service 的游戏：即使未检测到任何组件，也应将其视为受保护的游戏。

2. Research the living community (always; versions move)

2. 调研活跃的社区（始终执行；版本会变化）

Search, in order:
  1. "<game> modding" / "<game> mod loader" / "<game> modding wiki". The game's wiki often has a modding page.
  2. Nexus Mods (most popular mods show which frameworks they depend on), Thunderstore (Unity games: BepInEx packs), mod.io, the Steam Workshop (does the game have one? 
    um scan
    shows installed Workshop content).
  3. GitHub: "<game> mod", "<game> modding api", "<game> decompile", "<game> sdk", "<engine> mod loader".
  4. Recent posts (X/Reddit/Discord announcements) for new frameworks. The loader might be days old.
Capture: the loader's name, repo, current version and install steps, the game versions it supports, a "hello world" example mod, and where logs go.
按以下顺序搜索：
  1. “<game> modding”/“<game> mod loader”/“<game> modding wiki”。游戏 Wiki 通常会有 modding 页面。
  2. Nexus Mods（最热门的 mod 通常会显示其依赖的框架）、Thunderstore（Unity 游戏：BepInEx 套件）、mod.io、Steam Workshop（游戏是否支持？
    um scan
    会显示已安装的 Workshop 内容）。
  3. GitHub：“<game> mod”“<game> modding api”“<game> decompile”“<game> sdk”“<engine> mod loader”。
  4. 查看近期帖子（X/Reddit/Discord 公告）以了解新框架。加载器可能才发布几天。
记录：加载器名称、仓库、当前版本及安装步骤、支持的游戏版本、“hello world”示例 mod，以及日志位置。

3. Decide

3. 做出决定

  • Can it be modded safely? Look at anti-cheat, online-only parts, the EULA or mod policy, and the ownership checks that loaders rely on (see 
    skills/mod-any-game/references/safety.md
    ). If not: say so, and offer what is possible (official tools, offline modes, a different game with the same idea).
  • Route: loader API > data/asset mod > managed patching > native hooks > reimplementation/mashup. Pick the first that reaches the user's idea.
  • 能否安全地 mod？ 检查反作弊、仅在线部分、EULA 或 mod 政策，以及加载器所依赖的所有权检查（参阅 
    skills/mod-any-game/references/safety.md
    ）。如果不能，请明确说明，并提供可行的替代方案（官方工具、离线模式，或采用相同创意的其他游戏）。
  • 路线： loader API > 数据/资源 mod > managed patching > native hooks > reimplementation/mashup。选择第一个能够实现用户想法的路线。

4. Write MODDING_PLAN.md

4. 编写 MODDING_PLAN.md

markdown
undefined
markdown
undefined

<Game> modding plan

<Game> modding plan

  • Install: <path> (<store> <appid>), version <x>
  • Engine: <engine + version>, code: managed .NET / IL2CPP / native, 64-bit
  • Anti-cheat / online: <none | what + verdict>
  • Saves: <path> Config: <path> Logs: <path>
  • Community route: <loader vX.Y (repo)>, install: <steps>, example mod: <link>
  • Chosen route for "<idea>": <route> because <reason>
  • Lab plan: backup <folders> (um backup), lab profile <how>, windowed <how>
  • Unknowns to resolve first: <list>
Then continue with the mod-any-game loop (lab setup → source of truth → vertical slice).
  • Install: <path> (<store> <appid>), version <x>
  • Engine: <engine + version>, code: managed .NET / IL2CPP / native, 64-bit
  • Anti-cheat / online: <none | what + verdict>
  • Saves: <path> Config: <path> Logs: <path>
  • Community route: <loader vX.Y (repo)>, install: <steps>, example mod: <link>
  • Chosen route for "<idea>": <route> because <reason>
  • Lab plan: backup <folders> (um backup), lab profile <how>, windowed <how>
  • Unknowns to resolve first: <list>
然后继续执行 mod-any-game 循环（实验室设置 → 单一事实来源 → 垂直切片）。