QWE AI Academy Key takeaway: Claude Code (especially Opus 5.5) is steered away from full recreations of a specific existing title. Genre games, originals, and work from your own designs or assets stay in bounds. Framing and scope decide help vs a polite no – not “any game code.”
Late October into early November 2026 hit vibe-coders hard. Feeds filled with refusals. You need a playbook, not another headline stack.
What actually changed (short version)
Server-side flag tengu_heron_brook pushed new lines into Claude Code. Build originals, genre games, and games from the user’s own designs and assets. Don’t build a recreation of a specific existing game – even renamed, even labeled “original.” Community reverse of binary v2.1.314 (XDA) matched the screenshot text; no user toggle. Remote GrowthBook-style delivery only.
Using Claude to knock off someone else’s specific game breaks IP rules – so Anthropic added two sentences on Opus 5.5. That is the plain read from Addy Osmani (Anthropic technical staff, Oct 30 2026), as quoted in The Verge. Originals and own-asset paths were meant to keep working; he asked wrongly refused builders to ping him while they iterate.
Backdrop: AI decomps, browser ports, mashups. Indies got nervous about demos. Some preservation boards turned into token races. Anthropic drew the line at “specific existing game,” which also tracks the Usage Policy ban on infringing third-party IP (page notes around Nov 12 2026).
Method A vs Method B: what fails and what works
Two paths. Same model. Wildly different outcomes.
Method A – Direct recreate / “make me X but better”
- Names a commercial title or describes a 1:1 clone (including “new assets, new name”).
- Refusal on IP/policy. After a later pass, you often get “want an original game in that genre instead?” instead of a flat wall (Osmani follow-up; Tom’s ~Nov 5 2026).
- If the chat goal still reads as a copy, “clean-room art” talk does not save it.
Method B – Genre + own design + scoped technical help
- You bring the design doc, art, or binary you own.
- Ask for genre mechanics, debugging your code, or decompile/mod help – never “ship a clone of Title Y.”
- Turns out that class still moved: PCMag’s weekend on Opus 5.5 still decompiled Valheim-related mod work and got reverse-engineering help for personal mods/ports when the ask was not a full clone-in-service-of-copying.
Method B is how you keep shipping. Method A is exactly what the two sentences target.
Detailed walkthrough: prompts that still get work done
The catch is session shape. Keep chats narrow. Do not open with the full “I’m cloning Zelda” monologue.
1. Original or genre game from your brief
Build a top-down survival craft prototype in Godot 4.
My design notes (paste):
- day/night cycle, 3 resources, simple base building
- no existing IP names, characters, or level layouts
- use only placeholder colored shapes for now
Output: project structure + first playable scene scripts.Matches the allowed original / genre / own-design clause on the nose.
2. Mechanic study without title recreation
I need a double-jump + coyote-time controller in Unity.
Constraints: my own art, my own level. Explain the timing
window math and give a clean C# component I can drop in.
Do not reference or recreate any commercial game.Genre technique. No named product.
3. Owned binary / mod / port framing
I legally own this game build. Goal: personal mod and
achievement tracker that reads progress from decompiled
logic. Help me:
1) set up a static analysis workflow
2) map the save structure
3) write a read-only overlay
I will not redistribute assets or a full recreation.Same bucket PCMag saw proceed. “Rebuild the whole game with fresh art” did not.
Pro tip: Split the job. Chat A: explain this assembly/dump. Chat B: implement my original feature. Giant multi-goal threads that read like a full remake trip the steer harder.
Genuinely yours and still refused? Osmani invited those cases while they tune balance.
Edge cases and gotchas you’ll hit
| Task | Likely outcome (as of early Nov 2026) |
|---|---|
| Named full recreation / rename-and-claim-original | Blocked or redirected to original-in-genre |
| Genre prototype from your design doc | Allowed |
| Decompile/mod/port help on a copy you own, no clone goal | Often allowed (tests vary by phrasing) |
| Mid-project mechanic that “feels like” a famous game | Sometimes false positive |
| Personal digital version of a commercial board game | Reported refusals (GitHub / community) |
| Crash dumps, REA tool, anti-cheat, non-game RE | Intermittent blocks (possible separate cyber filters) |
No off switch. Collateral is real: halfway-through original projects and tabletop module work got hit; Tom’s Hardware collected crash-dump, anti-cheat, REA, and TV-firmware complaints beside the game rule. Hard-no already softened toward genre offers in some flows – expect more knobs behind the scenes.
One open question with no clean public answer: how the model decides “yours” vs “theirs” when the prompt is ambiguous. Docs never spell the classifier boundary.
Other models did not all copy the two-sentence fence. Pure preservation decomp, zero commercial clone intent? Some builders keep a second tool around. Stay inside the AUP either way – IP infringement is still a hard line, game flag or not.
FAQ
Does this mean Claude won’t help with any video game code?
No. Originals, genre sketches, and your own designs/assets are the intended yes-path.
Can I still reverse-engineer or mod a game I own?
Frame it as analysis or a personal mod on a build you own. Do not ask for a redistributable recreation of that specific game. After the change, testers still got decompile and port-oriented help when the thread stayed technical. “Make me a free Title X” dies immediately. Your local reverse-engineering laws still apply on top of Anthropic’s rules.
Why are crash dumps and anti-cheat requests failing too?
Not always the game sentences. Reports look like over-eager game-steer plus separate real-time cyber safeguards – unauthorized access and vuln work without authorization are restricted under the same usage policy, with a Cyber Verification Program for adjusted access. Own system, defensive scope: rephrase with ownership and a tight goal. Still blocked? Treat it as another filter and send feedback; do not assume the two-line game rule is the only gate.
Open Claude Code on a tiny original genre sketch – one screen, your rules, no famous title in the prompt – and lock a workflow on the allowed side of the line.