User profile support
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 14.4k
- Forks
- 1.3k
- PR merge metrics
- No merged PRs in 30d
Description
In order to create different settings and progress that don't depend on the logged-in user, we have to support user profiles. We have to think of information that is stored per-user (e.g. name) and extend the cvar system.
- What do we need to store per user?
- How are profiles switched?
- How do we store the data? (we probably want to preserve user comments)
We could maybe use nyan for storing the configuration, as that supports overlaying of data natively,
Contributor guide
No contributing guide indexed for this repository
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 mapping the existing cvar system and reviewing how nyan supports configuration overlays. Resolve the three open questions about per-user data, profile switching, and storage, including preservation of user comments; done means these decisions are implemented and covered by suitable tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100