Grok was allowed to change only the routines he named
The author built the browser game Hexwardia with Grok as the builder and Gemini as the checker. A 500-line file was not to be rewritten. Token use fell by more than 60%. Alpha v0.04.x is running live. Gemini found gold hoarding and a deadlocked pathfinder.
Done with GrokAdvanced
What was done
On 31 August 2026 the author writes that in two weeks he built Hexwardia, a turn-based 4X game in the browser, with Grok and Gemini. Grok wrote the combat engine, the fog of war, the procedural map generation and a heuristic AI. The 30 dollar plan, with Grok build, was the builder and the repository. The game is still served from grok.me, and the free tokens there were not enough. Gemini at 20 dollars was the checker and found silent bugs: the AI hoarded gold because the deficit math was wrong, and pathfinding deadlocked on buildings that could not be placed. When he showed a bug in a 500-line file, the model would rewrite the whole file or insert 10 functions he did not ask for. He required only the changed routines, with the same variable names and file contracts. That cut token use by more than 60%. The engine is running live in alpha, version v0.04.x, with no install, and it loads in under a second.
How it went
The game is running in alpha v0.04.x. Token use was cut by more than 60% when rewrites were refused. He does not say the gold bug and the pathfinding bug are fixed in the live version.
Worth knowing
More than 60% is his figure for the token cut. 30 dollars and 20 dollars are the plans he states. The post asks for a playtest and does not say what a player answered. The Gemini findings are described as findings, not as a finished fix.
How to do it
- Show the bug in the file it lives in, and require a diff only for the routines that should change.
- Ask the checker to look for silent bugs, and read the diff before it is applied.
- Do not publish the alpha again until you have seen that the named bugs are gone.
Try it with Grok
In [file] fix only [bug]. Return the diff for the routines that change, and keep the variable names. Do not rewrite the file. Do not publish until I say yes.
Replace text in brackets with your own.
Done when. The diff has been read, and nothing has been published without a yes.
Safety rule. No publish until you have said yes and read the diff.
Read the original
Read the original · u/Antique_Pair_140 on Reddit ·