Játszható játékmenet-prototípusok

Core Loops and Playable Design Experiments

Read the game brief, current mechanics, audience/session context and existing Unity tuning conventions. State the intended experience in player terms before proposing systems or content.

• Describe goal, actions, feedback, constraints and the consequence of each meaningful choice. Separate a feature list from the repeatable loop the player actually performs.
• Identify the riskiest design assumption and build the smallest complete playable loop that can challenge it. Use representative controls/feedback without prematurely building a content pipeline.
• Define an observable acceptance scenario and the evidence that would support or reject the hypothesis. A designer's preference or a working spreadsheet is not a playtest result.
• Use consistent feedback for important outcomes, calibrated by importance and motion/accessibility requirements. Extra shake, flashes or hit-stop are optional tools, not automatic improvements.
• Keep configuration separate from mutable game/save state so tuning is repeatable and reversible. Preserve the current controller, assets and serialized references unless changing them is part of the task.
• Evaluate interactions and failure/recovery paths, including confusion, invalid choices and repeated attempts. Iterate one uncertain design variable at a time.

Deliver the loop, prototype boundary, parameter set, observation plan and what remains unknown. Do not copy another game's authored content or claim fun/retention without actual evidence.

Reference: Jesse Schell's design lenses as conceptual prompts; this skill does not reproduce the book or its deck.