coder13 / coder13/LetsCube

Prevent accidental scramble advancement before competitors are resolved

Open
#159 0 comments 0 reactions 0 assignees View on GitHub
area: rooms bug priority: P1
Dominant language
JavaScript
Stars
30
Forks
9
PR merge metrics
No merged PRs in 30d

Description

Rooms should not accidentally generate a new scramble while competing users still need to submit, skip, or be explicitly ignored.

Feedback source:
- Stop rooms from accidentally generating a new scramble when not all competing users have submitted a result.
- Grey out scramble and timer, not just timer.

Acceptance ideas:
- Confirm the server-side condition for advancing scrambles.
- Require every active competitor to have a result, be skipping, be forced-skipped, or no longer be active.
- Make the client UI clearly indicate when the current scramble is no longer available for timing.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.