Repository navigation
Stalemate rule #9
Description
Activity
The status message on completion of the game should either be:
Stalemate. wins the game.
or
Stalemate. Draw game.
Status update:
- The stalemate timeout logic in
main.pyhas been changed to avoid importingtime. - Elapsed no-fruit time is now derived from tick counts multiplied by the configured
speed/tick_rate, whilegame-timeoutremains expressed in seconds. - This keeps hot-reload-safe config behavior and avoids wall-clock timing inside the game loop.
- I also updated the client-side competition-complete entry-screen countdown/status text to show
Next competition begins in: <Ns>during the reset delay.
I have not closed this yet because the existing
python tests/test_tournament.pycheck is currently hanging, so there is still follow-up verification/investigation to do.- The stalemate timeout logic in
Implementation reference:
- Server commit:
f614949(Add stalemate timeout and Sleepy Snake bot) - Client commit:
64d2a89(Improve competition status messaging) - Branch:
v401
The server commit implements the stalemate rule and includes
end_reasonin thegameoverpayload. The client commit updates the player/observer status text so stalemate wins mention that the winner was longer.- Server commit:
@copilot, review this issue and verify that it was implemented in a previous commit. Update this issue accordingly.
- linked a pull request that will close this issue[WIP] Fix stalemate rule implementation for game timeout #16
on Mar 13, 2026
If neither snake has collected any fruit within
game-timeoutseconds, end the current game. The winner is the longest snake, or if equal, the game is a draw.(Likely only needed when there is a fruit with a 0 (infinite) lifetime and the players are bots with cautious strategies.)