How to Review Video Games Playtesting, Critiques and Feedback.
Games are half about the game itself – the other half is about guidance.
• Let the game design itself silently guide the player. • Minimal reliance on text to convey information.
Copyright By PowCoder代写 加微信 powcoder
• How you are playing is secondary to what you are thinking. • Be vocal; talk out loud throughout.
• Avoid “I like it” or “I don’t like it”
• Use “I understand this part” and “I’m confused” instead.
• The player is never wrong, they just don’t know what the authors know.
Live Playtesting
Let the team know your thought processes, not just your actions
• “It seems like I might want to avoid this red ball because it’s red”
• “I don’t know what to do, I’ve tried WASD, space bar and arrow keys” • “I think I have to go up – so I’ll try to find a way to go up”
• “I died here, so I’ll retry but avoid that part – I’ll try jumping over it.”
• When you have given a good try and are still stuck, ask for guidance.
• Be professional. Don’t try to just compliment or criticize the game.
• Offer a summation of your thoughts at the end, and possibly some solutions for problems.
Team Note-taker
• Take notes on the problem, not a solution:
• “The playtester did not know what to do on level 2” is correct.
• “Make tutorial on level 2” is incorrect.
• The problem may be many other things, not just a need for a tutorial.
• If playtester states “The game is too hard”, it may be that only one mechanic is too difficult, the tester needed guidance, or the game has bugs.
• Encourage playtester to talk out loud so you can hear their thoughts.
• Avoid telling the playtester what to do unless they directly ask for help.
• Take notes on everything. Where were they stuck? Were they confused? What did they seem to understand?
• Have an assigned (not assumed) role.
Dev Teams Reviewing the Notes • Read between the lines of commentary
• Don’t take suggestions literally or directly
• Understand instead the frustration of the player
• Process feedback using suggestions from the entire team
• Determine how you will solve the issue – perhaps what the player really wanted
• Use threads of your feedback to identify issues
• If you repeatedly get the same note week after week, it may be a bigger issue • Do not be afraid to re-tool or tweak your game
• Don’t always add more, sometimes take things away from the game
Homework: Video Game Review (Online)
• Due: Individually, make a four or five-minute review of the mobile game ‘Spurpunk’ by playing it. Then post that video online.
• Put your review link in the GDD next to your name by next week.
• Critique the game, make any suggestions or insights you want.
• You can include your opinion of whether you like it or not. • State why – have reasons other than “It’s good/bad”
• At the end state if you recommend it or not – also state WHY.
• Make it professional – not “This is a class assignment for CS 526”.
• If you do that, it’s advertising a bias and no one watching will take you seriously.
• Reviewing it professionally will help you understand the goal of communication for your own game at midterms.
程序代写 CS代考 加微信: powcoder QQ: 1823890830 Email: powcoder@163.com