{"id":231,"date":"2021-04-05T17:27:00","date_gmt":"2021-04-05T21:27:00","guid":{"rendered":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/?p=231"},"modified":"2021-04-08T21:34:49","modified_gmt":"2021-04-09T01:34:49","slug":"playtesting","status":"publish","type":"post","link":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/?p=231","title":{"rendered":"Playtesting"},"content":{"rendered":"\n

Over the course of this semester, playtesting has been fundamental to our game development process. Every Friday during class time, we test our latest builds in-house; meanwhile, every Wednesday evening, we conduct external playtests to people who may or may not have played our game before. Playtesting allows us to identify bugs and get feedback on art and design choices, which then allows us to further iterate on our game. <\/p>\n\n\n\n

We approach our playtests with a general set of questions. For instance, every playtest we ask our volunteers if they are familiar with CMU buggy, and how comfortable they are with video games. If people are unfamiliar with the tradition of buggy, then we have the challenge of quickly familiarizing them with it in-game; if people aren\u2019t avid gamers, then we need to make sure our controls (like WASD for movement) are clear. 

<\/p>\n\n\n\n

\"\"
Our Controls\/Tutorial Screen, built in response to playtest feedback<\/figcaption><\/figure><\/div>\n\n\n\n

We also ask questions tailored towards our main focus at the time. Over these next few weeks, our specific questions will focus on:<\/p>\n\n\n\n

  • Art: Shadows and lighting<\/li>
  • Design: The tutorial screen, and button layout<\/li>
  • Code: How driving feels, player and opponent speeds, and notable differences in speed and acceleration among our buggy variations

    <\/li><\/ul>\n\n\n\n
    \"\"
    Track 1 with (newly added!) Shadows<\/figcaption><\/figure><\/div>\n\n\n\n

    We ask our questions in three parts: a pre-survey before playtesting, during the actual playtest, and in a post-survey. Typically, the pre-survey covers our more general questions, while the more specific questions are asked during or after the playtest. And sometimes, we don\u2019t even have to ask a question: we can observe the player and see for ourselves if the AI opponents are too fast, or if textures are glitching, or whatever else comes up during the playtest.  

    <\/p>\n\n\n\n

    \"\"
    Playtesting Bug: Endgame Leaderboard Glitch<\/figcaption><\/figure><\/div>\n\n\n\n

    After playtests are all said and done, the next thing to do is translate that feedback into action items and implement<\/em> them into the game. While that usually means fine-tuning what we\u2019ve already got, sometimes we end up implementing new features altogether. For example, players can now steer with arrows keys, instead of being restricting to just WASD. We reskinned our Distraction flag powerup, and made it Area-of-Effect (AOE)-activated.

    <\/p>\n\n\n\n

    • \"\"
      Old Distraction Flag design<\/figcaption><\/figure><\/li>
    • \"\"
      New Distraction Flag design<\/figcaption><\/figure><\/li>
    • \"\"
      Distraction Flag AOE indicator<\/figcaption><\/figure><\/li><\/ul><\/figure>\n\n\n\n


      As the semester goes on, we aim to do a lot more playtesting. With just a few weeks left until our final build, we look forward to sharing our game with the public. <\/p>\n","protected":false},"excerpt":{"rendered":"

      Over the course of this semester, playtesting has been fundamental to our game development process. Every Friday during class time, we test our latest builds in-house; meanwhile, every Wednesday evening, we conduct external playtests to people who may or may not have played our game before. Playtesting allows us to identify bugs and get feedback […]<\/p>\n","protected":false},"author":6,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_eb_attr":""},"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/index.php?rest_route=\/wp\/v2\/posts\/231"}],"collection":[{"href":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/index.php?rest_route=\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=231"}],"version-history":[{"count":20,"href":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/index.php?rest_route=\/wp\/v2\/posts\/231\/revisions"}],"predecessor-version":[{"id":295,"href":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/index.php?rest_route=\/wp\/v2\/posts\/231\/revisions\/295"}],"wp:attachment":[{"href":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=231"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=231"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/courses.ideate.cmu.edu\/53-472\/s2021\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}