DEDUPED We read 1,000+ AI sources. You read one email. Subscribe free

AI USE CASES

How to list types and methods in a Unity game with rea

Decode a Unity IL2CPP metadata file to see assembly images, type names and method names.

Authorization notice. rea is dual-use. Only use it on software, sites and systems you own or have explicit permission to test.

Who it is forGame modder or QA engineer who needs the class and method names in a shipped Unity game

The problemIL2CPP compiles game code to native, hiding the original type and method names.

The outcomeA list of assembly images, types and methods with index ranges from the metadata file.

What you need first

  • Node.js 22.x (>=22.19), 24.x (>=24.11), or 26+, plus npm
  • An MCP-capable AI agent such as Claude Code, Codex, Cursor or Gemini CLI
  • For native binaries: Hopper, Ghidra or IDA installed locally
  • For websites: a Chrome-family browser
  • On Linux: a procps-compatible ps on PATH for JavaScript/Electron analysis

Steps

  1. Locate the global-metadata.dat file from the game you are allowed to inspect.
  2. Run npx rea-agents setup and restart your agent.
  3. Ask the agent to inspect the IL2CPP metadata with REA.
  4. Ask it to summarize the types and methods related to the system you care about.

Prompt for your agent

Use REA to decode the IL2CPP metadata at <path to global-metadata.dat> and list assembly images, types and methods related to <system>. Verify names come from the decoded output.

Caveat. Static decoding supports metadata versions 29, 31 and 39 only. Check the game's terms before analyzing it.

About rea

A plug-in that lets your AI agent take apart an app and explain how a feature works. Part of this week's top 10 repos: ranked #1 on Repo Radar. View morluto/rea on GitHub.

More with rea

See all use cases for morluto/rea

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page