playtest-report

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
When invoked with
new
, generate this template:
markdown
undefined
当使用
new
参数调用时,生成如下模板:
markdown
undefined

Playtest Report

Playtest Report

Session Info

Session Info

  • Date: [Date]
  • Build: [Version/Commit]
  • Duration: [Time played]
  • Tester: [Name/ID]
  • Platform: [PC/Console/Mobile]
  • Input Method: [KB+M / Gamepad / Touch]
  • Session Type: [First time / Returning / Targeted test]
  • Date: [Date]
  • Build: [Version/Commit]
  • Duration: [Time played]
  • Tester: [Name/ID]
  • Platform: [PC/Console/Mobile]
  • Input Method: [KB+M / Gamepad / Touch]
  • Session Type: [First time / Returning / Targeted test]

Test Focus

Test Focus

[What specific features or flows were being tested]
[What specific features or flows were being tested]

First Impressions (First 5 minutes)

First Impressions (First 5 minutes)

  • Understood the goal? [Yes/No/Partially]
  • Understood the controls? [Yes/No/Partially]
  • Emotional response: [Engaged/Confused/Bored/Frustrated/Excited]
  • Notes: [Observations]
  • Understood the goal? [Yes/No/Partially]
  • Understood the controls? [Yes/No/Partially]
  • Emotional response: [Engaged/Confused/Bored/Frustrated/Excited]
  • Notes: [Observations]

Gameplay Flow

Gameplay Flow

What worked well

What worked well

  • [Observation 1]
  • [Observation 2]
  • [Observation 1]
  • [Observation 2]

Pain points

Pain points

  • [Issue 1 -- Severity: High/Medium/Low]
  • [Issue 2 -- Severity: High/Medium/Low]
  • [Issue 1 -- Severity: High/Medium/Low]
  • [Issue 2 -- Severity: High/Medium/Low]

Confusion points

Confusion points

  • [Where the player was confused and why]
  • [Where the player was confused and why]

Moments of delight

Moments of delight

  • [What surprised or pleased the player]
  • [What surprised or pleased the player]

Bugs Encountered

Bugs Encountered

#DescriptionSeverityReproducible
#DescriptionSeverityReproducible

Feature-Specific Feedback

Feature-Specific Feedback

[Feature 1]

[Feature 1]

  • Understood purpose? [Yes/No]
  • Found engaging? [Yes/No]
  • Suggestions: [Tester suggestions]
  • Understood purpose? [Yes/No]
  • Found engaging? [Yes/No]
  • Suggestions: [Tester suggestions]

Quantitative Data (if available)

Quantitative Data (if available)

  • Deaths: [Count and locations]
  • Time per area: [Breakdown]
  • Items used: [What and when]
  • Features discovered vs missed: [List]
  • Deaths: [Count and locations]
  • Time per area: [Breakdown]
  • Items used: [What and when]
  • Features discovered vs missed: [List]

Overall Assessment

Overall Assessment

  • Would play again? [Yes/No/Maybe]
  • Difficulty: [Too Easy / Just Right / Too Hard]
  • Pacing: [Too Slow / Good / Too Fast]
  • Session length preference: [Shorter / Good / Longer]
  • Would play again? [Yes/No/Maybe]
  • Difficulty: [Too Easy / Just Right / Too Hard]
  • Pacing: [Too Slow / Good / Too Fast]
  • Session length preference: [Shorter / Good / Longer]

Top 3 Priorities from this session

Top 3 Priorities from this session

  1. [Most important finding]
  2. [Second priority]
  3. [Third priority]

When invoked with `analyze`, read the raw notes, cross-reference with existing
design documents, and fill in the template above with structured findings.
Flag any playtest observations that conflict with design intent.
  1. [Most important finding]
  2. [Second priority]
  3. [Third priority]

当使用`analyze`参数调用时,读取原始测试记录,与现有设计文档交叉核对后,将结构化的分析结果填入上述模板中,同时标注所有与设计意图存在冲突的playtest观测结果。