feat (solos) add a play again button when the game is over.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
Research direction
Start with WinModel.ts and Main.ts, following the existing 1v1 and 2v2 requeue lifecycle. Verify that solo wins and deaths show the button, preserve the stated solo data while generating new identifiers, and trigger the normal fresh-game flow. Test the behavior in the browser and on Steam.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Add a play again button after a player has either died or has won a game in solo mode.
Describe the solution you'd like
WinModel.ts
- WinModel displays a play again button if its solos.
- Copies solo config and map settings, but generates a new game ID, client ID and timestamp.
- Send a matchmaking-requeue event with mode = "solo"
Main.ts
- The requeue handler which is used for 1v1 and 2v2, is now repurposed to also include "solo".
- Stores the restart data in
sessionStorageusing a new const key. - uses the same lifecycle for the window as requeuing in 1v1 or 2v2.
- The saved data is deleted from
sessionStorage - Normal join-lobby event runs to start a fresh solo game.
Assignment
- I'd like to be assigned to this issue and work on it myself
(already complete)
Should work on steam, however would recommend testing.
- Dominant language
- TypeScript
- Stars
- 2.7k
- Forks
- 1.4k
- Avg merge
- 16h 28m
- Merged PRs (30d)
- 332
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.
More from openfrontio/OpenFrontIO
-
not-approved
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openfrontio/OpenFrontIO#5562 · 1 comment ·
-
not-approved
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openfrontio/OpenFrontIO#5558 · 1 comment ·
-
not-approved
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openfrontio/OpenFrontIO#5556 · 1 comment ·
-
Newly added stations do not generate gold for trains already on their segment when placing them Opennot-approved
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
openfrontio/OpenFrontIO#5538 · 1 comment ·
-
not-approved
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openfrontio/OpenFrontIO#5500 · 1 comment ·
All issues in openfrontio/OpenFrontIO
Similar issues
-
comp/dashboard P3 type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
NousResearch/hermes-agent#117722 ·
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·