Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -102,7 +102,13 @@ $SecondBallTouchAllowed
@SetNoSecondBallContactVariable + value:true + r:false, @ForgetBallStartPosition + r:false

#DefensiveSetPlay
@ChangeAction + action:positioning, @ForgetBall, @LookAtFieldFeatures, @GoToFormationPosition + set_play:true + stand:true + enter_position:%placing_enter_position + leave_position:%placing_leave_position + enter_orientation:%placing_enter_orientation + leave_orientation:%placing_leave_orientation
$BallSeen
NO --> $ConfigRole
GOALIE --> $CountActiveRobotsWithoutGoalie
ZERO --> #SearchBall
ELSE --> #RolePositionWithPause
ELSE --> #SearchBall

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think only the striker should search the ball all others should go to the role position like we do during normal play. But I would change it so all robots do the wait + turn for a few seconds, but then only the config striker goes to search the ball and all others do to the role positions. If we add this to the search ball tree we can reuse it here with a simple ball seen decision.

@cleWu03 cleWu03 Sep 24, 2026 •

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since a change after the IFA game, where the config striker was out of field and no one else was searching the ball, this is the same behavior as during normal play. #1057 describes this problem further. We should find a solution where the decision who searches is not only based on the config role, to make sure exactly one robot does the search behavior in any cases. I like the idea of a U-Turn for all at the beginning, but would handle that in the fix for the other Issue, since it is not directly related to the problem of using the positioning capsule in a wrong moment

YES --> @ChangeAction + action:positioning, @LookAtFieldFeatures, @GoToFormationPosition + set_play:true + stand:true + enter_position:%placing_enter_position + leave_position:%placing_leave_position + enter_orientation:%placing_enter_orientation + leave_orientation:%placing_leave_orientation

#SetPlaySituation
$DoOnce
Expand Down
Loading