michaelplzno / michaelplzno/LoopTroupe.io-GDD
Choose room model for shared troupe loops
Open
Nobody has claimed this yet.
backend
research
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Decide whether loops are shared by room code, level instance, daily challenge, or global stage. Capture the persistence needs and griefing/moderation risks before hardening the backend.
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 with the issue's four proposed sharing scopes: room code, level instance, daily challenge, and global stage. Compare their persistence needs and griefing or moderation risks, then document the selected model and rationale. Done means the sharing scope and backend constraints are explicitly decided before implementation is hardened.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100