{"id":455,"date":"2019-04-05T14:54:27","date_gmt":"2019-04-05T14:54:27","guid":{"rendered":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/?p=455"},"modified":"2019-04-05T14:54:28","modified_gmt":"2019-04-05T14:54:28","slug":"3-25-3-29-week-10-something-got-done","status":"publish","type":"post","link":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/index.php\/2019\/04\/05\/3-25-3-29-week-10-something-got-done\/","title":{"rendered":"3\/25 – 3\/29 Week 10: Something got done"},"content":{"rendered":"\n

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

Week 10 has a lot of story to tell. We started our 3rd sprint, which is also the second last one, and aim for the playtest day, April 6th. The goal for this sprint is to finish the system building, implement the first half of the story and develop two mini games. As for the progress in Week 10, we are a little bit crunching.<\/p>\n\n\n\n


Production

<\/h3>\n\n\n\n

The user stories for sprint 3 is about \u201cprogression system\u201d and Story. Those are two crucial elements in our experience. It was a lesson that after implementing more parts of the game, more feedback came and we need more time to refine the previous part of the game. And it was longer than our expectation. So we need to rearrange the priority of tasks, so that we can still finish the sprint with most important things.<\/p>\n\n\n\n

Testing our game is a challenging task. First, our target audience is very specific, and hard to find. So we don\u2019t really have the right people to test for us. Second, we have to keep the competition problems secret, so we can only test with other problems. And last, our project is connected to our client\u2019s server, which creates some blocks for outside testers. In a word, we hope to make the best use of the playtest day and we appreciate ETC offers us this chance.<\/p>\n\n\n\n

– Magian <\/p>\n\n\n\n


Design

<\/h3>\n\n\n\n

For the past few weeks we have been struggling on coming up with minigame prototypes. Some concerns are as follows:<\/p>\n\n\n\n

  1. We needed to make sure that the minigames make sense to the story and fits in the world. We didn\u2019t want them to feel disconnected to the world, like a patch to the game that would seem awkward.<\/li>
  2. We needed to ensure that these games have replayability. Since minigames are the players\u2019 only way to earn token, we needed to make sure that the games are always accessible in a way but different every time.<\/li>
  3. We needed to make sure that the games are fun to play, as every game should be.<\/li><\/ol>\n\n\n\n

    Besides that, as we gradually shift into the later half of the semester, this also means that it\u2019s crunch time. We\u2019ve been busy coming up with art assets for each room as well as actually laying out theses spaces.<\/p>\n\n\n\n

    For this week, we\u2019ve finally began working on prototype \/ implementation of one of our minigames – typing test. We tested it within our team and we think that, although it has been commonly mocked as \u201chollywood hacking\u201d, the act of typing gibberish on computers really makes one feel like they\u2019re doing something ingenious and cool. We wanted to capture that sense of accomplishment, which is why we gave this idea a greenlight.<\/p>\n\n\n\n

    For the following week, we will be rolling out a few more minigames; we\u2019ll also work on playtests. Since we wanted players to win the game ultimately, difficulty is an extremely important measure to look out for and we will certainly pay attention to it.<\/p>\n\n\n\n

    – Brian<\/p>\n\n\n\n


    Tech

    <\/h3>\n\n\n\n

    This week, we\u2019ve been fleshing out the player experience. Players can now choose their own names from a list of 8, each associated with a color, which is currently used to distinguish the player\u2019s dialogues. The intro sequence has been adjusted several times based on user feedbacks to improve player experience.<\/p>\n\n\n\n

    We have replaced several old placeholder art assets with new ones, including the monitor frame for the intro and problem interface, replacing the computers lying around with cables, and the addition of a new room. Additionally, the terminal now shows a flashing caret to inform the player that it\u2019s waiting for player input.<\/p>\n\n\n\n

    \"\"\/<\/figure>\n\n\n\n
    \"\"\/<\/figure>\n\n\n\n
    \"\"\/<\/figure>\n\n\n\n

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

    – Max<\/p>\n\n\n\n

    Story<\/h3>\n\n\n\n

    This week we continued to write the script for our story up to Section 5, staying ahead of the tech team\u2019s implementation. We also discussed with the design team the details of how the mini-games will be incorporated into the script.<\/p>\n\n\n\n

    We\u2019re considering using LaTex as the software to write the script so that it can be easily parsed into an asset spreadsheet version, but we will need to be able to find time in the schedule to try this out.<\/p>\n\n\n\n

    – Tina<\/p>\n\n\n\n

    Art<\/h3>\n\n\n\n

    We completed the tileset for the plain room and the tiled portion of the ultra reality room. We added rocks, logs and tree stumps for the Forest room, which has been laid out.<\/p>\n\n\n\n

    We have completed several miscellaneous art tasks such as adding the tutorial wall and completing the player\u2019s dialogue portrait. We are now starting on the volcano room tiles.<\/p>\n\n\n\n

    Ultra-reality room tiles:<\/p>\n\n\n\n

    \"\"\/<\/figure><\/div>\n\n\n\n

    Plain room tiles:<\/p>\n\n\n\n

    \"\"\/<\/figure>\n\n\n\n

    Tutorial wall:<\/p>\n\n\n\n

    \"\"\/<\/figure>\n\n\n\n

    Volcano Room Concept<\/p>\n\n\n\n

    \"\"\/<\/figure><\/div>\n\n\n\n

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

    – Tina
    <\/p>\n\n\n\n

    For the next week, we\u2019re planning to:<\/p>\n\n\n\n

    >>> Continue Sprint 3 and finish it for playtest day.
    >>> Get idea of what we will be delivering by the end of the semester.
    >>> Plan our promotion video.<\/p>\n\n\n\n

    \"\"\/<\/figure><\/div>\n","protected":false},"excerpt":{"rendered":"

    Week 10 has a lot of story to tell. We started our 3rd sprint, which is also the second last one, and aim for the playtest day, April 6th. The goal for this sprint is to finish the system building, implement the first half of the story and develop two mini games. As for the […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-455","post","type-post","status-publish","format-standard","hentry","category-development-blogs"],"_links":{"self":[{"href":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/index.php\/wp-json\/wp\/v2\/posts\/455"}],"collection":[{"href":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/index.php\/wp-json\/wp\/v2\/comments?post=455"}],"version-history":[{"count":1,"href":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/index.php\/wp-json\/wp\/v2\/posts\/455\/revisions"}],"predecessor-version":[{"id":456,"href":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/index.php\/wp-json\/wp\/v2\/posts\/455\/revisions\/456"}],"wp:attachment":[{"href":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/index.php\/wp-json\/wp\/v2\/media?parent=455"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/index.php\/wp-json\/wp\/v2\/categories?post=455"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/projects-old.etc.cmu.edu\/brute4s\/index.php\/wp-json\/wp\/v2\/tags?post=455"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}