Support games with up to 6 players #26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Why
The engine currently allows 2 to 4 players (MAX_PLAYERS = 4) and in practice only 2-player games are generated or tested. Games with up to 6 players are required.
What I found (2026-10-06, probing the hand-written games with num_players 3 to 5)
Opp/ZWho::Oppmean "the next seat", which is only an opponent in 2-player games.omnia playand match seat alternation, CLI win counting, datagen zero-sum invariant.Plan
Oppas the next seat in turn order.Confidence
Medium: scope is from reading plus the probe; there may be more n-player assumptions in eval and training code to find.
Implemented on branch feature/six-player-games (commit
62b4d98), PR #27 stacked on #25. MAX_PLAYERS is 6; zero-sum payoff rule for any player count; new PRef::Target(i) because a chosen player target could not be referenced from effects at all (found while writing a multi-player game); evaluation, CLI and generator measurement are per seat; games/melee.ron is a six-player example. Tests cover 2 to 6 players across engine, validator, model batching, matches and measurement. Still open: no generator family makes more than two players, and deep-stack games need max_stack scaled with player count.