OneLiteFeatherNET / OneLiteFeatherNET/Voyager
Validate ring difficulty and boost balance with internal playtest
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 0
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 12
Description
Description
The firework boost mechanic (4s cooldown, vanilla formula) and ring placement have been implemented based on design assumptions but never validated with real players. An internal playtest session is needed to evaluate game feel and balance before opening to external testers.
Acceptance Criteria
- At least 3 internal team members play through the complete cup at least twice each
- Findings documented in
docs/research/alpha-playtest-01.md:- Ring pass rate (how many rings did players miss on average?)
- Boost usage patterns (did players use boosts at the right moments?)
- Perceived difficulty rating per map (1-5 scale)
- Any reported physics bugs or unfair ring placements
- At least one balance change is applied and re-tested based on findings
- Drift (game designer) signs off on the balance before opening alpha
Technical Details
- Use the dev-mode
/dev-startcommand to begin a race immediately - Playtest on the cup/map package from "Prepare cup/map data package" issue
- Document boost cooldown feel: does 4s feel punishing or fair?
Dependencies
- "Prepare cup/map data package for first closed alpha" must be done first
Estimate
S
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 with the /dev-start command and the cup/map package from “Prepare cup/map data package for first closed alpha.” Have at least three internal players complete the cup twice, then document ring misses, boost usage, map difficulty, physics issues, and ring fairness in docs/research/alpha-playtest-01.md. Apply and re-test one balance change, then obtain Drift’s sign-off.
Written by the indexing model from the issue text.
Assessment
- Domain
- game-dev, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100