Made by@gameforgePlaytest feedback
@gameforge/playtest-feedback
Turn messy playtest notes into a ranked list of what to fix next. Tags each note (bug, confusion, frustration, boredom, delight, idea), tallies them with a script, ranks issues by how many testers hit them and how badly, and lists the moments players loved so you protect them.
- Activity
- New: be the first to try it
- Installs
- 0 installs
- Likes
- 0 likes
- Clones
- 0 clones
- 1# Playtest feedback
- 3Paste in what your playtesters said and get back a ranked list of what to fix next, plus the moments players loved so you do not break them. A small script does the counting, so the ranking is the same every time.
- 5**Who it is for:** indie and jam developers, students, and small teams who just ran a playtest and have a pile of notes, chat messages, or form answers.
- 7## Example
- 9Input, `data/playtest.csv` (Claude builds this from your raw notes):
- 11```
- 12tester,level,type,severity,tag,note
- 13P1,1-2,frustration,2,jump-too-floaty,Overshot the small platform three times
- 14P2,1-2,frustration,3,jump-too-floaty,Gave up on the gap after 6 tries
- 15P2,1-3,bug,3,stuck-in-wall,Got stuck inside the wall left of the door
- 16P3,1-3,delight,,,Coin sound is really satisfying
- 17```
- 19Output, `out/playtest-summary.md`:
- 21| # | Issue | Type | Testers | Worst | Where |
- 22| - | ----- | ---- | ------- | ----- | ----- |
- 23| 1 | jump-too-floaty | frustration | 4/4 | 3 | 1-2 |
- 24| 2 | stuck-in-wall | bug | 2/4 | 3 | 1-3 |
- 26Plus a per-level table, a "Protect these" list of delights, tester ideas, and a short "Fix next" section with a concrete change to try for each top issue. Try it with `examples/playtest.csv`.
- 28## What it can access
- 30- Runs its own script, `node scripts/tally-playtest.mjs`.
- 31- Reads raw notes from `playtests/` and `data/`; writes `data/playtest.csv` and reports in `out/`.
- 32- No network, no env vars.
- 34## Setup
- 36None. Needs Node.js 18 or newer.