Back to AI game news
AI game news

Veto Protocol lets players edit AI boss attack plans mid-fight

By GameSlash

Released November 14 for Epic AI MegaJam, the Unreal game has five plan-editing bosses and a documented Claude Code workflow for deterministic previews and automated tests.

Wonho Lee released Veto Protocol: Director's Cut on itch.io on November 14, 2026 for the Epic AI MegaJam. Rather than simply fighting robot bosses, players edit the bosses' planned moves as the battle continues. The project also documents how Claude Code helped create Unreal Engine C++ gameplay and test a deterministic preview system, making this more than another AI-assisted game upload.

First official Veto Protocol gameplay screenshot from Wonho Lee's itch.io gallery
Developer's original gameplay screenshot: Wonho Lee / Veto Protocol. Shown for editorial reporting, not a generated replacement.

Beat the boss by changing its next moves

A boss displays a film-strip plan card: MOVE, SWING, FIRE BEAM and other actions advance one step per musical beat. The player can strike out a future action or swap two future steps in real time while dodging. Reordering a beam can make it destroy its own shield pylon; editing drone instructions can make the drones crash into each other. Five bosses have different rules, and the final Director can veto the player's first edit. The creator reports three possible endings.

How the AI development workflow was tested

The developer wrote a single tile-grid simulator, VetoSim, and used that same logic both for the floor's ghost preview and for actual boss execution. That avoids a common puzzle-game problem where the preview promises a result the game engine then simulates differently. According to the developer's detailed devlog, eight automated test groups include preview-versus-execution, legal edit validation, a Director veto test and three endings. For each boss, 150 automatically generated cards were checked to ensure the unedited sequence was safe and a legal edit could force the boss to harm itself. The developer reports zero failures in that test set; GameSlash has not independently reproduced it.

Second distinct official gameplay screenshot showing Veto Protocol's battle interface
Another image from the official Veto Protocol gameplay gallery by Wonho Lee.

What AI actually produced, and where humans intervened

The solo creator says Claude Code wrote Unreal Engine 5.8 C++ and Blender automation scripts under human direction. All game models were built in Blender with agent-authored scripts, rather than a text-to-3D model service. Google Flow concept drawings were only reference material, not in the released screenshots or game. The developer says seven music tracks were generated with Google Flow Music, sound effects synthesized in Python, and voice lines produced with Piper TTS using declared voice-data sources. A late mock evaluation pushed changes to the tutorial, HUD, camera visibility and pause menu.

The devlog explicitly notes two limitations: the automated player is too good at reading the preview to demonstrate real difficulty, and the developer wanted one more check of Google Flow Music's publication terms. Those are the creator's disclosures, not GameSlash's own testing or rights assessment.

Players can download the approximately 337 MB Windows 10/11 build from Veto Protocol on itch.io. The full making-of devlog explains the design changes and test conditions.

View source