{"id":254,"date":"2018-02-27T19:56:48","date_gmt":"2018-02-28T00:56:48","guid":{"rendered":"https:\/\/projects-old.etc.cmu.edu\/enigma\/?p=254"},"modified":"2018-03-10T13:29:07","modified_gmt":"2018-03-10T18:29:07","slug":"dev-blog-week-6","status":"publish","type":"post","link":"https:\/\/projects-old.etc.cmu.edu\/enigma\/index.php\/2018\/02\/27\/dev-blog-week-6\/","title":{"rendered":"Dev blog: Week 6"},"content":{"rendered":"

Progress<\/p>\n

In week 6 we turned on the engine and moved forward to producing.<\/p>\n

Following the suggestions from the instructors:<\/p>\n

    \n
  1. List some questions that we have to clarify our clients\u2019 thought and request, to help us make design decisions.<\/li>\n
  2. Assign more specific roles in team to better distribute responsibility.<\/li>\n
  3. Set milestones for the project in order to make the progress more clear.<\/li>\n
  4. Finish research mode and get into produce mode.<\/li>\n
  5. For everything we do, think of how it will push the project or help the project.<\/li>\n<\/ol>\n

     <\/p>\n

    With the feedback from quarters, we asked questions to our client and got very important answers which would lead us to make future design decisions\uff1a<\/p>\n

      \n
    1. A clarification of relationship between our experience and the bigger experience (figure below).\u00a0We can design an experience that stands alone itself and can be played itself, and they will fit it into the bigger experience later.<\/li>\n<\/ol>\n

      \"\"<\/p>\n

        \n
      1. Use historical event results, fictional characters and storylines is fine.<\/li>\n
      2. Digital props, game can be played with just printed material and App.<\/li>\n
      3. The number of scenes and roles: we can decide according to our design need.<\/li>\n<\/ol>\n

        Also we divided our designers into 3 different roles:<\/p>\n

        Experience designer (Sally), who\u2019s in charge of the players\u2019 experience, the flow of the whole experience, the form of each activity, and how the emotion arc goes.<\/p>\n

        Puzzle designer (Howard), who\u2019s going to design puzzles in the puzzle solving scenes.<\/p>\n

        Narrative designer (Victoria), who\u2019s going to write the detailed story out and design the roles with background stories individually.<\/p>\n

         <\/p>\n

        Challenges<\/p>\n

        Although we divided the design team into different roles, the intersection in different roles make the responsibility not very clear, and people didn\u2019t know where exactly to start. We still had to spend long time in meetings to keep everyone in the same page.<\/p>\n

        Besides, the design of the prop in the App is still waiting for puzzles to come out. Our programmers built a basic structure of the App, however it really needs more information to go forward.<\/p>\n

        Decisions & Plans<\/p>\n

        As results of this weeks work, we had an experience map of players to illustrate roughly how the players will play and feel during the game.<\/p>\n

        Also we had a lot of mechanics of puzzles that could be potential puzzles in the game.<\/p>\n

        Narrative wise, we playtested and decided the sequence of information that will be discovered by the players, which is time+bomb — 3 suspicious — Coventry.<\/p>\n

        \"\"<\/p>\n

        \"\"<\/p>\n

        \"\"<\/p>\n

        Our plan next week is to get feedbacks from our client on the three aspects, and make a demo version of whole experience to playtest.<\/p>\n","protected":false},"excerpt":{"rendered":"

        Progress In week 6 we turned on the engine and moved forward to producing. Following the suggestions from the instructors: List some questions that we have to clarify our clients\u2019 thought and request, to help us make design decisions. Assign more specific roles in team to better distribute responsibility. Set milestones for the project in […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[],"class_list":["post-254","post","type-post","status-publish","format-standard","hentry","category-dev-blog"],"_links":{"self":[{"href":"https:\/\/projects-old.etc.cmu.edu\/enigma\/index.php\/wp-json\/wp\/v2\/posts\/254"}],"collection":[{"href":"https:\/\/projects-old.etc.cmu.edu\/enigma\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/projects-old.etc.cmu.edu\/enigma\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/enigma\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/enigma\/index.php\/wp-json\/wp\/v2\/comments?post=254"}],"version-history":[{"count":3,"href":"https:\/\/projects-old.etc.cmu.edu\/enigma\/index.php\/wp-json\/wp\/v2\/posts\/254\/revisions"}],"predecessor-version":[{"id":266,"href":"https:\/\/projects-old.etc.cmu.edu\/enigma\/index.php\/wp-json\/wp\/v2\/posts\/254\/revisions\/266"}],"wp:attachment":[{"href":"https:\/\/projects-old.etc.cmu.edu\/enigma\/index.php\/wp-json\/wp\/v2\/media?parent=254"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/enigma\/index.php\/wp-json\/wp\/v2\/categories?post=254"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/enigma\/index.php\/wp-json\/wp\/v2\/tags?post=254"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}