Skip to content

Releases: RoboCup-SSL/ssl-game-controller

v2.15.7

24 Apr 14:44
Compare
Choose a tag to compare
More debug logging for geometry

v2.15.6

24 Apr 11:43
Compare
Choose a tag to compare
Automatically request robot substitution on too many robots

v2.15.5

23 Apr 08:12
Compare
Choose a tag to compare
Fix: Consider removal time for yellow cards only during RUNNING

v2.15.4

21 Apr 16:54
Compare
Choose a tag to compare
Fix detection of invalid goal due to fouls

v2.15.3

20 Apr 20:40
Compare
Choose a tag to compare
Add timestamp to fouls to make invalid goal detection work

v2.15.2

07 Apr 18:56
Compare
Choose a tag to compare
Fix GitHub Release pipeline

v2.15.0

07 Apr 17:19
Compare
Choose a tag to compare
Replace gobuffalo/packr with go embed

v2.14.4

03 Apr 14:20
Compare
Choose a tag to compare
Change offset to grace period of 2s from now

v2.14.3: Avoid getting stuck due to missing ball placement command

15 Mar 20:04
Compare
Choose a tag to compare
It is still possible to get stuck if there are two game events after each other, both stopping the game. The second one will cancel the ball placement in this case.

v2.14.2: Avoid getting stuck due to missing ball placement command

09 Mar 20:04
Compare
Choose a tag to compare
It is currently possible, especially during dribble fouls, that the ball is still within the 1m radius where no ball placement is required. But if it is moving, it can get out of this radius. Currently, the check for ball placement is only done immediately after the STOP command. So the game is stuck in a situation, where ball placement is required, but no command is sent.