v3.0.0

Release for RoboCup 2024.

Changes w.r.t. v1.0.0 (RoboCup 2023):

• Removed support for 2023 technical challenges.
• Added support for Shared Autonomy Challenge.
  • Note: The button that switches to the Set state is still called Ready. It starts a Ready state with a duration of 1ns before transitioning to Set.
• Added some options for testing (disable delays, endless penalty shoot-outs, unpenalize players immediately).
  • Can be activated individually via CLI or launcher.
• Added delayed Ready state for Champions Cup.
• Added Standby state.
• Added Forbidden Motion in Standby penalty.
  • The Motion in Set button changes to Motion in Standby during the Standby state.
• Changed Global Game Stuck to alternating kick-off.
  • The button appears in place of the Set button during the Playing state.
• Updated RoboCupGameControlData.
  • Increased version to 18.
  • Removed COMPETITION_TYPE_DYNAMIC_BALL_HANDLING.
  • Added COMPETITION_TYPE_SHARED_AUTONOMY.
  • Added STATE_STANDBY.
  • Added PENALTY_SPL_ILLEGAL_MOTION_IN_STANDBY.

Changes w.r.t. v2.0.0 (German Open 2024):

• Added Standby state.
  • Changed Motion in Initial to Motion in Standby.
  • Picking up a player with the Motion in Standby penalty changes its penalty time to 60 seconds because the Pick-up penalty also counts down during Ready.
  • Penalty timers aren't cleared anymore at the transition to Ready. This doesn't really change anything as the only penalty in Initial was Pick-up which didn't start a timer in Initial anyway. However, it makes a difference now with the Forbidden Motion in Standby penalty.
• Added support for Shared Autonomy Challenge.
  • Note: The button that switches to the Set state is still called Ready. It starts a Ready state with a duration of 1ns before transitioning to Set.
• Updated RoboCupGameControlData.
  • Increased version to 18.
  • Added STATE_STANDBY.
  • Renamed PENALTY_SPL_ILLEGAL_MOTION_IN_INITIAL to PENALTY_SPL_ILLEGAL_MOTION_IN_STANDBY.

While Challenge Shield teams do not need to handle the new constants STATE_STANDBY and PENALTY_SPL_ILLEGAL_MOTION_IN_STANDBY (they can never be sent in Challenge Shield games), they still need to accept the new version number.

v3.0.0-rc.1

First release candidate for RoboCup 2024.

Changes w.r.t. v1.0.0 (RoboCup 2023):

• Removed support for 2023 technical challenges.
• Added support for Shared Autonomy Challenge.
  • Note: The button that switches to the Set state is still called Ready. It starts a Ready state with a duration of 1ns before transitioning to Set.
• Added some options for testing (disable delays, endless penalty shoot-outs, unpenalize players immediately).
  • Can be activated individually via CLI or launcher.
• Added delayed Ready state for Champions Cup.
• Added Standby state.
• Added Forbidden Motion in Standby penalty.
  • The Motion in Set button changes to Motion in Standby during the Standby state.
• Changed Global Game Stuck to alternating kick-off.
  • The button appears in place of the Set button during the Playing state.
• Updated RoboCupGameControlData.
  • Increased version to 18.
  • Removed COMPETITION_TYPE_DYNAMIC_BALL_HANDLING.
  • Added COMPETITION_TYPE_SHARED_AUTONOMY.
  • Added STATE_STANDBY.
  • Added PENALTY_SPL_ILLEGAL_MOTION_IN_STANDBY.

Changes w.r.t. v2.0.0 (German Open 2024):

• Added Standby state.
  • Changed Motion in Initial to Motion in Standby.
  • Picking up a player with the Motion in Standby penalty changes its penalty time to 60 seconds because the Pick-up penalty also counts down during Ready.
  • Penalty timers aren't cleared anymore at the transition to Ready. This doesn't really change anything as the only penalty in Initial was Pick-up which didn't start a timer in Initial anyway. However, it makes a difference now with the Forbidden Motion in Standby penalty.
• Added support for Shared Autonomy Challenge.
  • Note: The button that switches to the Set state is still called Ready. It starts a Ready state with a duration of 1ns before transitioning to Set.
• Updated RoboCupGameControlData.
  • Increased version to 18.
  • Added STATE_STANDBY.
  • Renamed PENALTY_SPL_ILLEGAL_MOTION_IN_INITIAL to PENALTY_SPL_ILLEGAL_MOTION_IN_STANDBY.

While Challenge Shield teams do not need to handle the new constants STATE_STANDBY and PENALTY_SPL_ILLEGAL_MOTION_IN_STANDBY (they can never be sent in Challenge Shield games), they still need to accept the new version number.

v2.0.0

This is a GameController that is functionally equivalent to that used at the German Open 2024.

v2.0.0-rc.3

Third release candidate for German Open 2024.

Changes w.r.t. second release candidate:

• Add separate CC/CS competitions for German Open
• Set larger and unified window height (for some reasons, the default height that works on other systems isn't sufficient on the GameController PCs, maybe because Wayland counts the window decoration as part of the size?)
• Taking a timeout during the half-time break when the timer is already negative ignores the negative part of the secondary time. This makes timeouts in the half-time break "interleaved" games much less confusing.

Changes w.r.t. v1.0.0 (2023):

• Removed support for 2023 technical challenges.
• Added some options for testing (disable delays, endless penalty shoot-outs, unpenalize players immediately).
  • Can be activated individually via CLI or launcher.
• Added delayed ready state.
• Added Forbidden Motion in Initial penalty.
  • The Motion in Set button changes to Motion in Initial during the Initial state.
• Changed Global Game Stuck to alternating kick-off.
  • The button appears in place of the Set button during the Playing state.
• Updated RoboCupGameControlData.
  • Increased version to 16.
  • Removed COMPETITION_TYPE_DYNAMIC_BALL_HANDLING.
  • Added COMPETITION_TYPE_SHARED_AUTONOMY.
  • Added PENALTY_SPL_ILLEGAL_MOTION_IN_INITIAL.

v2.0.0-rc.2

Second release candidate for German Open 2024.

Changes w.r.t. first release candidate:

• Added complete list of German Open 2024 teams.
• Fixed default window height for German Open.
• Added a workaround to ignore team messages during the delayed Initial state (#54).

Changes w.r.t. v1.0.0 (2023):

• Removed support for 2023 technical challenges.
• Added some options for testing (disable delays, endless penalty shoot-outs, unpenalize players immediately).
  • Can be activated individually via CLI or launcher.
• Added delayed ready state.
• Added Forbidden Motion in Initial penalty.
  • The Motion in Set button changes to Motion in Initial during the Initial state.
• Changed Global Game Stuck to alternating kick-off.
  • The button appears in place of the Set button during the Playing state.
• Updated RoboCupGameControlData.
  • Increased version to 16.
  • Removed COMPETITION_TYPE_DYNAMIC_BALL_HANDLING.
  • Added COMPETITION_TYPE_SHARED_AUTONOMY.
  • Added PENALTY_SPL_ILLEGAL_MOTION_IN_INITIAL.

v2.0.0-rc.1

First release candidate for German Open 2024.

Changes w.r.t. v1.0.0 (2023):

• Removed support for 2023 technical challenges.
• Added some options for testing (disable delays, endless penalty shoot-outs, unpenalize players immediately).
  • Can be activated individually via CLI or launcher.
• Added delayed ready state.
• Added Forbidden Motion in Initial penalty.
  • The Motion in Set button changes to Motion in Initial during the Initial state.
• Changed Global Game Stuck to alternating kick-off.
  • The button appears in place of the Set button during the Playing state.
• Updated RoboCupGameControlData.
  • Increased version to 16.
  • Removed COMPETITION_TYPE_DYNAMIC_BALL_HANDLING.
  • Added COMPETITION_TYPE_SHARED_AUTONOMY.
  • Added PENALTY_SPL_ILLEGAL_MOTION_IN_INITIAL.

v1.0.0

This is a GameController that is functionally equivalent to that used at RoboCup 2023.

v1.0.0-rc.2

This is the second release candidate of the GameController to be used at RoboCup 2023.

• Please read the README.md. It is not a complete manual yet, but it points out a few important differences to the old (Java) GameController.
• Check if your team colors are set correctly in config/teams.yaml.
• The format of RoboCupGameControlData and RoboCupGameControlReturnData (in game_controller_msgs/headers/RoboCupGameControlData.h) hasn’t changed since the last announcement on March 28.
• For the In-Game Visual Referee Challenge, the format for reporting results is described in game_controller_msgs/headers/VisualRefereeChallenge.h and hasn’t changed either since the announcement on March 28.
• The Team Communication Monitor / Game State Visualizer is still maintained in the old repository and works with the new GameController. The log files are not compatible, though.
• Report issues either here on GitHub or via email to Arne Hasselbring.

Notable changes since v1.0.0-rc.1:

• Fixed receiving of team messages
• Advanced networking options are hidden by default (by Jayen Ashar)
• Added code to evaluate the Data Minimization Challenge
• Added basic capability to replay log files
• Linux binary should work on some older systems (glibc >= 2.28 is still required)

v1.0.0-rc.1

This is the first release candidate of the GameController to be used at RoboCup 2023.

• Please read the README.md. It is not a complete manual yet, but it points out a few important differences to the old (Java) GameController.
• Check if your team colors are set correctly in config/teams.yaml.
• The format of RoboCupGameControlData and RoboCupGameControlReturnData (in game_controller_msgs/headers/RoboCupGameControlData.h) hasn’t changed since the last announcement on March 28.
• For the In-Game Visual Referee Challenge, the format for reporting results is described in game_controller_msgs/headers/VisualRefereeChallenge.h and hasn’t changed either since the announcement on March 28.
• The Team Communication Monitor / Game State Visualizer is still maintained in the old repository and works with the new GameController. The log files are not compatible, though.
• Report issues either here on GitHub or via email to Arne Hasselbring.
• It is known that the provided Linux binaries do not work on Ubuntu 20.04. You can report working / not-working distributions in #37 or via email to Arne Hasselbring.

Errata:

• 4b3e3b7 broke receiving of broadcast team messages. Has been fixed in 545e22a and will be part of v1.0.0-rc.2.

v0.9.2

• Allow some penalties in more states
• Build only an aarch64 binary on macOS