What this template helps you decide
Capture the intended play style, input behavior, timing, tuning variables, audiovisual feedback, edge cases, and balance tests for one weapon. The prompts are written for production use, so each section leads to a rule, dependency, measurable target, or test case.
The download is a portable `.gddkit` project. It includes formatted Markdown, tables, a version entry, and Mermaid diagrams where a state or flow is easier to understand visually.
Design intent
Describe the situation where this weapon is the best choice and the tradeoff that prevents it from replacing every alternative.
Controls
Document buffering, held inputs, interruption, target selection, aim assist, movement, stamina, ammo, heat, and network authority.
Tuning
Keep derived values such as damage per second separate from authored values. State the test assumptions behind every target.
Keep the spec small enough to review. Link this focused document from the main GDD, then record material changes in the project changelog.
How to use it with your team
- Name the player-facing goal before describing implementation.
- Replace every placeholder with a rule, number, owner, or open question.
- Mark assumptions that require a prototype or playtest.
- Review dependencies with design, engineering, art, audio, and QA.
- Export the approved version to PDF and keep later decisions in the changelog.
Use it as part of a complete GDD
A focused system spec should not duplicate the project vision, overall scope, or shared technical constraints. Keep those in the main game design document template and use this file for the details that need concentrated review.