Fast bootstrapping of patches
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 766
- Forks
- 51
- Avg merge
- 16d 14h
- Merged PRs (30d)
- 1
Description
This would only download the most necessary data of each patch (game version data in particular) on initial patch selection, with the rest being only downloaded when needed (e.g. once a particular game has been located on a user's system).
In particular, this means:
- Only pull
versions.jsfor every patch after stack configuration - Use that to start searching for games
- Download any global patch data during the search process
- Create shortcuts
- Download/update the rest of each game's data individually after the user started a game through a shortcut, using a blocking downloader.
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
Start by tracing patch selection and the downloader flow described in the issue. Use versions.js as the initial per-patch data source, then map the search, shortcut creation, and per-game update steps. Done means initial selection fetches only versions.js, while remaining data is fetched when a game is started.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100