No description
Find a file
2020-09-02 12:45:05 -07:00
.github Update main.yml 2020-07-29 10:49:50 -07:00
.gitignore Create .gitignore 2020-01-01 17:48:46 -08:00
go.mod init go module 2020-01-01 17:46:01 -08:00
go.sum Add "EliminatedBy" to snake eliminations. (#11) 2020-02-19 11:44:48 -08:00
LICENSE Add standard LICENSE 2020-01-01 17:40:37 -08:00
README.md Update README.md 2020-09-02 12:45:05 -07:00
royale.go Add static seed to royale rulset. 2020-07-29 13:14:42 -07:00
royale_test.go Add static seed to royale rulset. 2020-07-29 13:14:42 -07:00
ruleset.go Fix function name and interface tests. 2020-05-17 14:38:39 -07:00
solo.go Add solo gameplay ruleset. 2020-05-17 14:29:30 -07:00
solo_test.go Fix function name and interface tests. 2020-05-17 14:38:39 -07:00
squad.go Rename TeamRuleset -> SquadRuleset 2020-07-21 14:58:56 -07:00
squad_test.go Rename squad tests to avoid name collisions. 2020-07-25 17:35:20 -07:00
standard.go Ensure snakes eating on their last turn survive! 2020-08-31 13:18:03 -07:00
standard_test.go Add tests to ensure that head-to-heads on food remove the food. 2020-08-31 13:30:09 -07:00

BattlesnakeOfficial/rules

codecov

Battlesnake rules and game logic.

FAQ

The Y-Axis appears to be implemented incorrectly?

This is because the game rules implement an inverted Y-Axis. Older versions of the Battlesnake API operated this way, and several highly competitive Battlesnakes still rely on this behaviour and we'd still like to upport them. The current game engine accounts for this by translating the Y-Axis (or not) based on which version of the API each Battlesnake implements. More info here and here.

In the future we might switch this to make the rules easier to develop? But until we drop support for the older API version it doesn't make sense to make that change.