codecombat / codecombat/codecombat
Don't lock out replayable challenges if browser crashes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 8.6k
- Forks
- 4.2k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 39
Description
My browser crashed in the middle of submitting Sarven Siege. This caused the submit to be aborted and the submit in a day to be displayed. I believe I would have won the challenge again, and would rather not have to wait 24 hours every time the browser glitches. I've been simulating games in 2 other tabs and this has occurred quite a few times where Chrome fails. Is there a way to flush the cache in an event like this?
Can we think of a way to do this that's immune to just closing the browser window if you are about to lose?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified in the issue. Start by reproducing a browser crash during Sarven Siege submission and trace how the submission and 24-hour cooldown are recorded. Done means an interrupted submission is handled fairly without allowing deliberate browser closure to bypass challenge limits.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- game-dev, web-dev
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100