Aborting a placement with a force start causes side effects about ssl-game-controller HOT 3 CLOSED

After more detailed analysis:

On step 4: the game is continued with a force start after the ball placement. The normal action would have been a Direct Free with a 5s timer.

This timer also continues to run after the force start, and when the ball is placed inside the defense area to wait for the Keeper Held Ball 1.1s were still remaining on the Direct Free timer.

The Keeper Held Ball foul is then only issued after 6.1 s instead of the expected 5s.

It also correlates to what is seen with the placement timer. As soon as the placement timer ran down to 0s it takes 5s until the foul is issued.

from ssl-game-controller.

The problem can also be reproduced using the official GC UI and not only the Sumatra Refbox.

There has to be a STOP between the Direct Free and the Force Start. This stop also pauses the 5s Direct Free timer, so it might not be so uncommon for this to happen.

from ssl-game-controller.

The currentActionTimeRemaining was not reset for commands like STOP or FORCE_START. The noProgressDetector waits for the timer to reach zero. That's why it took longer after a canceled ball placement. The remaining time of the ball placement had to pass, before the no-progress timer started to count.

from ssl-game-controller.