-
Notifications
You must be signed in to change notification settings - Fork 4
[Server]: Fix Puzzles Navigation #277
Copy link
Copy link
Open
Labels
D3Hard DifficultyHard DifficultyP3High PriorityHigh PriorityS26Current relevant issue that should be worked on in the spring 2026 semesterCurrent relevant issue that should be worked on in the spring 2026 semesterapprovedThis issue has passed the draft stage, and is ready to be assignedThis issue has passed the draft stage, and is ready to be assigned
Description
Metadata
Metadata
Assignees
Labels
D3Hard DifficultyHard DifficultyP3High PriorityHigh PriorityS26Current relevant issue that should be worked on in the spring 2026 semesterCurrent relevant issue that should be worked on in the spring 2026 semesterapprovedThis issue has passed the draft stage, and is ready to be assignedThis issue has passed the draft stage, and is ready to be assigned
Type
Fields
Give feedbackNo fields configured for issues without a type.
Task Description:
Right now, the puzzles navigation towards the board is just kinda... weird. Specifically there's 2 main issues. One is that they seem to get selected, move towards the nearest deadzone, ALWAYS move clockwise around the deadzone until they reach the top of the board and specifically the column in which they need to go down, and then proceed to drop downwards like in a game of Connect 4.
However, not only is this inefficient, but collisions aren't even checked - when the piece drops down from the top deadzone, it doesn't care if there's any pieces in the way and just passes through them. This is clearly a problem, and needs to be fixed.
The second issue we found is that when you finish a puzzle and begin to start another puzzle, for pieces not currently on the board, it will do the above movement as normal. However, if it is wanting to move a current piece (i.e one involved in a previous puzzle to a different position), it will do something weird. It will send them ALWAYS directly towards the bottom left deadzone cell in the corner regardless of what pieces it must bulldoze to get there, and then continues moving clockwise as normal.
Your job is to debug these tasks and fix them by implementing a better movement system for moving pieces into place for puzzles. You also want to fix the 2nd issue if it still exists after task #276 is finished but the error persists.