When should you use it?
- A mod needs to change behavior enforced in native code
- Single-point patches keep failing
- You own the game and the community allows mods
Not for: Online or anti-cheat protected games; Bypassing DRM or license checks
What do you need, and what do you get?
You need
- Your own copy of the game binary
- A disassembler
- Notes on what fails today
You get
- Map of every place the rule is enforced
- List of patch sites with original and new bytes
- Patch script and backup
How does it work, step by step?
- Back up the binaryKeep an untouched copy and hash it so you can always restore.
- Name the behaviorDescribe exactly what is blocked and what you have already tried.
- Trace callersHave the agent find the function that enforces it and every place it is called.
- Group the call sitesMap each call to the game area it belongs to, so you can test area by area.
- Patch and test in passesChange one area at a time, run the game, and keep a log of each patch's bytes and effect.
The prompt
Our own prompt, inspired by u/CelebrationFew1755 on r/ClaudeAI and written to work in Claude Code. Values in lime are placeholders.
Fill in the blanks (optional; the copied prompt uses your values)
Binary: {binary_path} (I own this copy; offline single-player use). Behavior to change: {restriction}. Already tried: {attempts}. 1. Find the function that enforces this and list every call site with address and the code area it sits in. 2. For each call site, explain the conditional branch that follows in plain English. 3. Propose the smallest patch per site, showing original and new bytes. 4. Give me a test order, one area at a time. Do not modify the file yourself.
Inspired by u/CelebrationFew1755 on r/ClaudeAI: I used Claude Code to reverse engineer a 13-year-old game binary and crack a restriction nobody had solved — the community is losing it. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.
What can go wrong?
- Patching one call site and declaring victory; the other checks still fire.
- Hooks into scripting state can crash the game; prefer static patches.
Our take
The lesson that carries over to any legacy software problem is the inventory step. The breakthrough came from finding all thirteen places the rule was enforced instead of patching the obvious one. Asking an agent to list every caller, group them, and explain the branch after each call turns a guessing game into a checklist. Add a hash and backup before any byte changes, and a patch log so others can review exactly what was altered. Work only on software you own or have rights to modify. Test each patch pass in an isolated environment. Prefer community-reviewed diffs over opaque binaries when sharing. Do not use these techniques against online games' anti-cheat in ways that violate terms or law. Keep notes of failed hypotheses. Merging, deploying and deleting stay with a person. Verify the final build hash against your patch log. Share patches as diffs with checksums so others can validate before applying them.
Where the time goes back: The agent does the slow part of reverse engineering, following every caller of one function, which the poster says took under a day.
FAQ
Do I need assembly knowledge?
Is this legal?
Source and credit
Inspired by u/CelebrationFew1755 on r/ClaudeAI. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.
- Inspired by
- I used Claude Code to reverse engineer a 13-year-old game binary and crack a restriction nobody had solved — the community is losing it
- Creator
- u/CelebrationFew1755 on r/ClaudeAI
- Published on
- Original date
- Mar 15, 2026
- License
- Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
- Originally for
- Claude Code
- AI dry run
- Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails. - Verified
- Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.
Are you the creator? Claim or correct this page.