How to use Claude to balance faction game AI
Claude Code tuned opposing faction players through headless simulations. Human rule fixes and turn GIF inspection checked active play alongside near-even wins.
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Run opposing faction players through the headless simulator and preserve suspicious matches as turn GIFs. Separate core rule defects from player goal-weight tuning, check active engagement as well as win rates and ask me to approve rule changes before resuming balance experiments.
Reach people exploring AI agents
See placements →What happened
The developer reports more active faction play and near-even simulated wins after core rule fixes and agent iteration. Turn GIFs supported review; universal game balance is not established.
Reported by twistedweasel — itch.io devlogHow the agent did it
- The developer ran headless faction matches and identified passive play and core rule problems.
- After human rule fixes, two agents optimized opposing players through repeated simulations.
- The developer inspected exported turn GIFs while evaluating engagement and win balance.
Where a person stepped in
The developer repaired core rules before tuning players, assigned opposite faction objectives and inspected exported turns from suspicious runs.
The developer of Caleb's Hollow used Claude Code to iterate on goal-based faction players through a headless simulator. The first large set of AI-versus-AI matches did not produce useful balance: players could remain passive, and tweaking their parameters alone did not address the underlying game problems.
The human first corrected core balance issues. Then two agents received opposite faction objectives and permission to change the player code. They repeatedly ran simulations, adjusted goal weights and introduced objectives that made the factions engage rather than merely survive.
The simulator could export the state of each turn as a GIF. That gave the developer a way to inspect a suspicious game and distinguish a real strategy from a misleading win count. The reported iteration eventually approached even wins while both factions actively contested the game.
The outcome is a more credible set of simulated players and a concrete balance-testing workflow, according to the devlog. It does not demonstrate universal balance or replace human judgment of the rules. The important distinction in the account is that the developer fixed the game before tuning agents, and checked visible match behavior alongside aggregate results. An even score alone would have concealed the earlier passive play.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: itch.io devlog · twistedweasel
Frequently asked questions
Why were the first simulations insufficient?
Players could remain passive, and parameter changes did not fix core game problems.
How were suspicious matches inspected?
The simulator exported the state of each turn as a GIF.
Does an even win rate prove balance?
No. The author also checked engagement, and the result is limited to the reported simulations.
More details
About this account
The developer ran headless faction matches and identified passive play and core rule problems. After human rule fixes, two agents optimized opposing players through repeated simulations.
Original devlog and exact-date index opened. Near-even wins are the author's simulation result, not a proof of balance across every strategy or seed. Suggested prompt written by Agents In Use; no original task prompt was published in the verified account.
Credit: twistedweasel — itch.io devlog
Source published 8 Apr 2026
Source checked 14 Oct 2026
Tools and topics
Claude Code · Headless simulator · GIF exports
Game balance · AI players
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.