{"id":453,"date":"2019-08-30T20:57:20","date_gmt":"2019-08-30T20:57:20","guid":{"rendered":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/?p=453"},"modified":"2019-12-11T20:57:21","modified_gmt":"2019-12-11T20:57:21","slug":"beatem-postmortem","status":"publish","type":"post","link":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/2019\/08\/30\/beatem-postmortem\/","title":{"rendered":"Beat’em Postmortem"},"content":{"rendered":"\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

Beat’Em is a rhythm-action game in which guests punch and kick at robots in a 360\u00b0 arena to the beat of music. It’s designed as an arcade experience so that multiple people could play it in a short amount of time.\u00a0 An online leaderboard for the game was created so guests could see how their scores stacked up against others.<\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t

\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
<\/div>\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t
\n\t\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t

<\/p>\n

Platform: Vive<\/p>\n

<\/p>\n

Players: 1<\/p>\n

<\/p>\n

Controllers: 2 Vive Controllers & 2 Vive Trackers<\/p>\n

<\/p>\n

Rhythm Style: Note Highway<\/p>\n

<\/p>\n

\u00a0<\/h2>\n

<\/p>\n

Punching<\/h3>\n

<\/p>\n

The primary interaction in Beat\u2019em is punching. Robots float towards the player, who must punch them once they reach the strum cage. The strum cage is a series of transparent lines surrounding the player that represents when the notes should be hit. The name comes from Guitar Hero\u2019s strum line, like the one seen below:<\/p>\n

<\/p>\n

\"This<\/figure>\n

<\/p>\n

Robots come in several distinct colors. These colors help differentiate them and tell players how they should interact with the bots. Pink robots, for example, may only be hit by the player\u2019s left hand, while blue robots may only be hit by their right. The robots came towards the player at two different heights.<\/p>\n

\u00a0<\/p>\n

<\/p>\n

\"This<\/figure>\n

<\/p>\n

Hitting a robot with the wrong hand leads to a missed note.<\/p>\n

<\/p>\n

\"This<\/figure>\n

<\/p>\n

\u00a0<\/h3>\n

Kicking<\/h3>\n

<\/p>\n

Yellow robots appear near the ground and must be kicked by players.<\/p>\n

<\/p>\n

\"This<\/figure>\n

<\/p>\n

\u00a0<\/h3>\n

Arm Cross<\/h3>\n

<\/p>\n

At certain points in the song, a ring of purple robots surrounds the player. When this happens, players must cross their arms over their chest to create a bubble around themselves. When the robots hit the strum line, players release their arms from their chest, exploding the bubble and destroying the robots.<\/p>\n

<\/p>\n

\"This<\/figure>\n

<\/p>\n

\u00a0<\/h3>\n

Accuracy<\/h3>\n

<\/p>\n

Players are awarded more points for hitting robots closer to the music\u2019s beats. They receive visual feedback that tells them if their hits were Good, Great, Perfect, or Misses. Since kicks were harder to perform accurately, all kicked yellow robots awarded Perfect accuracy.<\/p>\n

<\/p>\n

\"This<\/figure>\n

<\/p>\n

\u00a0<\/h3>\n

Combos & Multipliers<\/h3>\n

<\/p>\n

As players hit robots consecutively without missing, they gain a combo. Each robot hit in a row adds one to the combo. Missing any robot resets the combo to zero. A multiplier (based on the combo) gives players more points. Players normally earn x1 points, but at a combo of 10 earn x2, at a combo of 20 earn x4, and so on to x8. When combos reset, multipliers reset as well.<\/p>\n

<\/p>\n

\"This<\/figure>\n

<\/p>\n

\u00a0<\/h2>\n

<\/p>\n

    \n
  • Gameplay is easily-understood<\/li>\n
  • Fun to play<\/li>\n
  • Fun to watch<\/li>\n
  • Replayable<\/li>\n
  • Cycle guests through quickly<\/li>\n
  • Sense of progression\/comparison to everyone else<\/li>\n<\/ul>\n

    <\/p>\n

    We feel that the project successfully reached these goals, as the final product was accepted into Festival and had a long line of eager guests waiting to play.<\/p>\n

    <\/p>\n

    \u00a0<\/h2>\n

    Iteration Thoughts:<\/h2>\n

    <\/p>\n

    Design<\/h3>\n

    <\/p>\n

      \n
    • Simple, quick motions were easy to understand and perform in high-pressure situations. Punching and kicking are both simple, brief motions, which is necessary since they were done in quick sequence.<\/li>\n
    • Kicking was satisfying for players. Games typically don\u2019t include mechanics using players\u2019 feet as well as their hands, and kicking is a very visceral, enjoyable motion.<\/li>\n
    • Bots lead players around the arena. Rather than have robots come from any direction, we made sure to have them lead the player in a circle. That way, players always knew where to expect the next ones.<\/li>\n
    • The strum cage gave guests a visible indicator of when to hit the robots, which helped increase accuracy.<\/li>\n
    • The arm-cross motion was very complex compared to the punching or kicking motions. Punching and kicking involved a single, straightforward motion. The arm-cross, on the other hand, involved both arms moving with two distinct actions – moving together and moving apart. Once players understood the action, they enjoyed it a lot more.<\/li>\n
    • The accuracy of punching is related to depth perception (calibration).<\/li>\n<\/ul>\n

      <\/p>\n

      Programming<\/h3>\n

      <\/p>\n

        \n
      • Tools made prototyping different concepts very easy\n
          \n
        • An in-game beatmapping tool made it very simple to come up with initial beatmaps. The specific notes could be adjusted later, but the initial concept came from the in-game tool.<\/li>\n
        • The beatmaps were converted to .csv files, which made them very easy to load into Excel and alter.<\/li>\n<\/ul>\n<\/li>\n
        • Player & NoteController classes got bloated<\/li>\n
        • Didn\u2019t really follow OOP<\/li>\n
        • The data saving from scriptable objects to csv files was not smooth.\u00a0\u00a0<\/li>\n
        • Some feedback features only worked in editor, never made it into the build.<\/li>\n<\/ul>\n

          <\/p>\n

          Art<\/h3>\n

          <\/p>\n

            \n
          • Using different, distinct colors for the robots made it much easier for players to differentiate and therefore correctly hit the robots.<\/li>\n
          • The robots had very simple designs, which didn\u2019t distract guests.<\/li>\n
          • We had different text and particle effects for Good, Great, and Perfect hits. These allowed the player to easily and quickly gain a sense of how they were doing.<\/li>\n
          • The robots came out of portals around the map. Having these portals open and close gave players and indication of where robots would be coming from next.<\/li>\n
          • We wanted to differentiate our notes from other VR rhythm games like Beat Saber or Audioshield, which both use red\/orange and blue notes. We tried other combinations of colors, but found that reddish and bluish colors are different and easily understood by guests.<\/li>\n<\/ul>\n

            <\/p>\n

            Music<\/h3>\n

            <\/p>\n

              \n
            • Music with strong beats made it much easier to follow the rhythm and act accordingly.<\/li>\n
            • Using an ABA musical form allowed us to divide the music into different sections, each with their own distinct patterns and moments.<\/li>\n
            • Using musical repetition (repeating a similar primary melody) allowed us to instill familiarity and confidence in guests and increase the complexity of interactions, building off of previous interactions.<\/li>\n
            • It proved difficult to change the length of the overall experience. We needed a short experience but found that we couldn\u2019t integrate all the musical ideas we developed. We shortened the intro and took out a middle chunk since we couldn\u2019t change the tempo to fit the time constraint.<\/li>\n
            • The dense arrangement of music made it difficult to fine-tune sound effects so that they were loud and noticeable enough for players.<\/li>\n<\/ul>\n

              <\/p>\n

              \u00a0<\/h2>\n

              Lessons Learned<\/h2>\n

              <\/p>\n

              VR<\/h3>\n

              <\/p>\n

              List<\/p>\n

              <\/p>\n

                \n
              • Simple, single-action motions are easiest to perform.<\/li>\n
              • Lead guests with visual clues, especially in a 360\u00b0 space.<\/li>\n
              • VR games typically require continuous actions rather than discrete. You must consider how players move to get from one note to the other, since some motions are physically impossible.<\/li>\n<\/ul>\n

                <\/p>\n

                Note Highway<\/h3>\n

                <\/p>\n

                  \n
                • Providing strum line\/cage is very important for players to be able to play well.<\/li>\n
                • Giving several types of feedback (visual & auditory) helps players understand how they\u2019re doing.<\/li>\n<\/ul>\n

                  <\/p>\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

                  Beat’Em is a rhythm-action game in which guests punch and kick at robots in a 360\u00b0 arena to the beat of music. It’s designed as an arcade experience so that multiple people could play it in a short amount of […]<\/p>\n","protected":false},"author":2,"featured_media":462,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[12],"tags":[],"class_list":["post-453","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-postmortems","col-lg-4 col-md-6"],"_links":{"self":[{"href":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/wp-json\/wp\/v2\/posts\/453"}],"collection":[{"href":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/wp-json\/wp\/v2\/comments?post=453"}],"version-history":[{"count":6,"href":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/wp-json\/wp\/v2\/posts\/453\/revisions"}],"predecessor-version":[{"id":467,"href":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/wp-json\/wp\/v2\/posts\/453\/revisions\/467"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/wp-json\/wp\/v2\/media\/462"}],"wp:attachment":[{"href":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/wp-json\/wp\/v2\/media?parent=453"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/wp-json\/wp\/v2\/categories?post=453"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/jam-session\/index.php\/wp-json\/wp\/v2\/tags?post=453"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}