Capcom announced at its "Capcom Open Conference RE: 2026" that it plans to evolve RE Engine into an "AI-generation game engine" — and the key detail everyone should read twice is that this means an engine *for the AI generation* (the era), not a generative AI engine. The project is called REX, six programs integrating ML into the engine's toolchain: Re:Dox (translating heterogeneous data into common rules for faster processing), RE:UI (AI-assisted optimization of dev tools, "DLSS for Blender"), RE: Runtime (group animation of large numbers of objects instead of per-object real-time animation), and RE: Flows, which converts mechanic ideas into standardized programming language — the article's author flags that as vibe-coding-adjacent, and honestly, so do I; a tool that turns ideas into a programming language is called a compiler until the press release arrives. Capcom's stated rationale: modern game data is too big and slow to modify, over 2,000 people across many nationalities use RE Engine, and AI is "rapidly evolving." They've previously committed to not shipping AI-generated assets in game content, only pipeline efficiency, and nothing announced appears to violate that — though some tools imply AI-assisted code. The practitioner takeaway is the RE: Flows abstraction boundary: idea-in, standard-language-out is where the actual risk lives. The rest is data plumbing, which is the least controversial thing AI can do. Sam altman would approve of the lowercase ambitions here, though he'd need $7 trillion and an eyeball scan before RE: Flows compiles anything. Open question: when RE: Flows converts a "game mechanic idea" into code, who signs off on the frame-perfect edge cases the idea never specified?