Offer an optional timed challenge mode

Open
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
frontend, game-dev

Research direction

Start by reading the delivered untimed submit-and-reveal journey before defining the timed-mode boundaries. Add deterministic timer-state tests covering pause, resume, navigation, reload, and submission, then verify keyboard and screen-reader behavior; done means all acceptance criteria are met without changing untimed results.

Written by the indexing model from the issue text.

Description

Goal

Offer an explicitly optional timed challenge mode for players who want speed-based play without changing the default untimed experience.

Background

Timing is unsuitable as the core loop because play is frequently interrupted. Any timed mode must be entered deliberately and remain isolated from ordinary hunts and their results.

Acceptance criteria

  • Untimed play remains the default and contains no running timer.
  • Timed mode requires an explicit mode choice before a hunt begins.
  • Timing start, pause, resume, interruption, and submission rules are defined before implementation.
  • Leaving the page or locking the device does not create a misleading result.
  • Timed and untimed results are stored and presented separately.
  • The timer is accessible without producing disruptive repeated announcements.
  • No public leaderboard or account is introduced.
  • Players can abandon timed mode without affecting an untimed saved hunt.

Verification

  • Add deterministic timer-state tests.
  • Exercise pause, resume, navigation, reload, and submission scenarios.
  • Verify the timer with keyboard and screen-reader-oriented semantics.

Dependencies

  • The untimed submit-and-reveal journey must be delivered and accepted first.
Dominant language
JavaScript
Stars
1
Forks
0
Avg merge
5m
Merged PRs (30d)
14

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from glowkeeper/rectangle-react

All issues in glowkeeper/rectangle-react

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.