{"id":357,"date":"2025-04-03T18:48:24","date_gmt":"2025-04-03T18:48:24","guid":{"rendered":"https:\/\/projects.etc.cmu.edu\/expression\/?p=357"},"modified":"2025-04-30T16:17:38","modified_gmt":"2025-04-30T16:17:38","slug":"week-11-prepare-for-soft","status":"publish","type":"post","link":"https:\/\/projects.etc.cmu.edu\/expression\/week-11-prepare-for-soft\/","title":{"rendered":"Week 11: Prepare for Soft"},"content":{"rendered":"\n

Playtest Success & Feedback<\/strong><\/h2>\n\n\n\n

Our Playtest Day went successfully \u2014 we had 25 participants and received a wide range of valuable feedback.<\/p>\n\n\n\n

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

User Experience & Interaction<\/h3>\n\n\n\n
    \n
  • Many players didn\u2019t realize they could only visit one location, leading to confusion and frustration. This needs clearer communication.<\/li>\n\n\n\n
  • Several tried to click the \u201cForum\u201d button, assuming it was functional. Lack of feedback on disabled elements led to confusion.<\/li>\n\n\n\n
  • The log feature was heavily used by some players for decision-making, but others found it offered little help in early choices.<\/li>\n\n\n\n
  • Some players attempted to interact with elements (like phones or dorm items) after paths had ended, indicating a need for better flow or guidance.<\/li>\n\n\n\n
  • Players unfamiliar with games struggled more with navigation, while experienced players progressed faster.<\/li>\n<\/ul>\n\n\n\n

    Content & Narrative<\/h3>\n\n\n\n
      \n
    • Some players felt disoriented by a lack of character context, especially when choosing between characters like Poli, Law, and Norma.<\/li>\n\n\n\n
    • Backgrounds and motivations were unclear to some users, leading to confusion about the relevance of conversations.<\/li>\n\n\n\n
    • Meta-questions like \u201cHow well do you understand this topic?\u201d felt forced and unnatural in dialogue. Testers preferred these to be part of quizzes.<\/li>\n\n\n\n
    • Real-world references (e.g., CMU names\/policies) created misunderstandings, making players think they were learning about actual school policies.<\/li>\n\n\n\n
    • Some players appreciated the new ideas (like content-neutral security fees) but felt uncertain about their accuracy. Suggestion: verify with a subject matter expert (SME).<\/li>\n<\/ul>\n\n\n\n

      Bugs & Technical Issues<\/h3>\n\n\n\n
        \n
      • Several visual and interaction bugs were found:
        \n
          \n
        • Cutscene\/Background bugs<\/strong> in auditorium (disappearing or misaligned).<\/li>\n\n\n\n
        • Character misplacement<\/strong>, especially Law’s position.<\/li>\n\n\n\n
        • Sprite inconsistencies<\/strong>, particularly Poli\u2019s expression changing inappropriately.<\/li>\n\n\n\n
        • \u201cTo be continued\u201d screen<\/strong> appears incorrectly when exiting phone mid-scene, with a typo (\u201ccontinued\u201d).<\/li>\n\n\n\n
        • Buttons not resetting properly<\/strong>, e.g., “Meet the Team” stays highlighted.<\/li>\n\n\n\n
        • Profile screen back button<\/strong> doesn\u2019t work when opened from the phone.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n

          Replayability & Flow<\/h3>\n\n\n\n
            \n
          • Some players replayed the game but were frustrated they had to go through the same prologue again.<\/li>\n\n\n\n
          • Strong desire for a chapter select or \u201cskip prologue\u201d feature to streamline replays and encourage exploring alternate paths.<\/li>\n\n\n\n
          • Some players tried alternate character paths but encountered blocked or bugged phone quizzes in second playthroughs.<\/li>\n<\/ul>\n\n\n\n

            Pacing & Reading Load<\/h3>\n\n\n\n
              \n
            • Multiple testers mentioned there was a lot of reading\u2014some neutrally, others critically.<\/li>\n\n\n\n
            • Skipping or fast-forwarding was instinctive for some players, especially those used to games.<\/li>\n\n\n\n
            • Players suggested the game might be better as a website for accessibility, due to the static nature and text-heavy format.<\/li>\n<\/ul>\n\n\n\n

              Player Suggestions<\/h3>\n\n\n\n
                \n
              • Clarify what\u2019s fictional vs. real to avoid misunderstandings about institutional policies.<\/li>\n\n\n\n
              • Add pronouns to profiles for clarity and inclusivity.<\/li>\n\n\n\n
              • Use Live2D or basic animations to make conversations more engaging (if time allows).<\/li>\n\n\n\n
              • Consider small visual enhancements (e.g., screen shakes, flashes) to make the experience more dynamic<\/li>\n<\/ul>\n\n\n\n
                \"\"<\/figure>\n\n\n\n
                \n\n\n\n

                Some of the points raised aligned with known issues, while others brought up unexpected bugs and offered new suggestions. We\u2019re incredibly grateful for the thoughtful responses, and after reviewing all the feedback, we compiled a detailed list of features, fixes, and content needs moving forward:<\/p>\n\n\n\n

                Post-Playtest Task List<\/strong><\/h2>\n\n\n\n

                Narrative<\/strong><\/h3>\n\n\n\n
                  \n
                • Court dialogue<\/li>\n\n\n\n
                • Endings<\/li>\n\n\n\n
                • Iterate Day 1 dialogue\n
                    \n
                  • Auditorium joke<\/li>\n\n\n\n
                  • Prologue: clarify step-sibling backstory<\/li>\n<\/ul>\n<\/li>\n\n\n\n
                  • Forum content<\/li>\n<\/ul>\n\n\n\n

                    Design<\/strong><\/h3>\n\n\n\n
                      \n
                    • Affection point system<\/li>\n<\/ul>\n\n\n\n

                      Art<\/strong><\/h3>\n\n\n\n
                        \n
                      • Adjust sprite positioning to match dialogue<\/li>\n\n\n\n
                      • New sprites for the court scene<\/li>\n\n\n\n
                      • Iterate speaker cutscene<\/li>\n\n\n\n
                      • Refine character and background art<\/li>\n\n\n\n
                      • Create cutscenes for court, main menu, and endings<\/li>\n<\/ul>\n\n\n\n

                        Tech<\/strong><\/h3>\n\n\n\n
                          \n
                        • Skip dialogue feature<\/li>\n\n\n\n
                        • Chapter\/save-load system<\/li>\n<\/ul>\n\n\n\n

                          Bugs<\/strong><\/h3>\n\n\n\n
                            \n
                          • Sprite\/name mismatch<\/li>\n\n\n\n
                          • Options bug (“another question” reappearing)<\/li>\n\n\n\n
                          • Text message display bugs<\/li>\n\n\n\n
                          • Forum display issues<\/li>\n\n\n\n
                          • Hyperlink system for key terms<\/li>\n<\/ul>\n\n\n\n

                            UI<\/strong><\/h3>\n\n\n\n
                              \n
                            • Add location names (e.g., gym, court)<\/li>\n\n\n\n
                            • Improve phone UX (currently always shows 9:41, add daytime lock for review access, etc.)<\/li>\n\n\n\n
                            • Complete phone UI for texts and forum<\/li>\n\n\n\n
                            • Credits page<\/li>\n<\/ul>\n\n\n\n

                              Sound<\/strong><\/h3>\n\n\n\n
                                \n
                              • Court BGM and SFX<\/li>\n\n\n\n
                              • Auditorium SFX<\/li>\n\n\n\n
                              • Ending BGM<\/li>\n<\/ul>\n\n\n\n
                                \n\n\n\n

                                Top Priority<\/strong><\/h2>\n\n\n\n
                                  \n
                                • Court Dialogue<\/li>\n\n\n\n
                                • Affection Point System<\/li>\n\n\n\n
                                • Endings<\/li>\n\n\n\n
                                • Cutscenes<\/li>\n<\/ul>\n\n\n\n

                                  The affection point system is tightly tied to the choice design in Day 2. Without proper values and balancing, the branching narrative can\u2019t function properly. Endings are also essential for delivering closure and giving the scoring system actual meaning\u2014without them, the player\u2019s decisions lack weight.<\/p>\n\n\n\n

                                  Medium Priority<\/strong><\/h3>\n\n\n\n
                                    \n
                                  • Cutscenes (new ones for Day 2 & endings)<\/li>\n\n\n\n
                                  • Skip dialogue feature<\/li>\n\n\n\n
                                  • Phone functionalities (text messages + forum)<\/li>\n\n\n\n
                                  • Chapter\/load\/save system<\/li>\n<\/ul>\n\n\n\n

                                    For a narrative-heavy game, visuals are key to maintaining player engagement. Cutscenes give us a chance to emotionally amplify story beats and break up long passages of text. Even rough versions will help \u2014 we\u2019ll polish them later if time allows.<\/p>\n\n\n\n

                                    The forum must also be functional by Soft Opening. Since the button is already visible in the UI, leaving it inactive will confuse players. Similarly, text messages are a small but essential way to convey transitions and off-screen events \u2014 they\u2019re more visually appealing and intuitive than just using in-dialogue exposition.<\/p>\n\n\n\n

                                    The skip feature is another must-have. Currently, Day 1 takes around 10 minutes to play through, mainly because of slow text display. Adding this function will help with both replayability and user pacing.<\/p>\n\n\n\n

                                    Lower Priority<\/strong><\/h3>\n\n\n\n
                                      \n
                                    • Background and sprite refinements<\/li>\n\n\n\n
                                    • Hyperlink explanations for legal\/academic terms<\/li>\n\n\n\n
                                    • Iterating older cutscenes<\/li>\n<\/ul>\n\n\n\n

                                      These are all improvements we\u2019d love to make, but only after higher-priority systems are solidified.<\/p>\n\n\n\n

                                      \n\n\n\n

                                      Production Reflections<\/strong><\/h2>\n\n\n\n

                                      Looking back, we realized that not having a game designer has led to a few structural oversights\u2014like not implementing the affection point system from the start. It became clear through this playtest that scoring systems need to be in place early to inform branching choices and dialogue structure.<\/p>\n\n\n\n

                                      Our approach in Day 1 was to write full dialogue and choices first, then assign affection point outcomes based on how each character would logically react. While this made sense narratively, it left the overall system unbalanced. Going forward, we\u2019ll design with player choice and system integration in mind from the start.<\/p>\n\n\n\n

                                      Fortunately, now that Day 1 is mostly complete, building Day 2 will be much faster, as the core mechanics and pipelines are already in place.<\/p>\n\n\n\n

                                      \n\n\n\n

                                      Next Steps Before Soft Opening<\/strong><\/h2>\n\n\n\n
                                        \n
                                      • Finish all top-priority features and content<\/li>\n\n\n\n
                                      • Selectively complete medium-priority items based on workload<\/li>\n\n\n\n
                                      • Push all remaining tasks to post-soft sprint<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"

                                        Playtest Success & Feedback Our Playtest Day went successfully \u2014 we had 25 participants and received a wide range of valuable feedback. User Experience & Interaction Content & Narrative Bugs & Technical Issues Replayability & Flow Pacing & Reading Load Player Suggestions Some of the points raised aligned with known issues, while others brought up […]<\/p>\n","protected":false},"author":2,"featured_media":365,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-357","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/projects.etc.cmu.edu\/expression\/wp-json\/wp\/v2\/posts\/357","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/projects.etc.cmu.edu\/expression\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/projects.etc.cmu.edu\/expression\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/projects.etc.cmu.edu\/expression\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/projects.etc.cmu.edu\/expression\/wp-json\/wp\/v2\/comments?post=357"}],"version-history":[{"count":4,"href":"https:\/\/projects.etc.cmu.edu\/expression\/wp-json\/wp\/v2\/posts\/357\/revisions"}],"predecessor-version":[{"id":400,"href":"https:\/\/projects.etc.cmu.edu\/expression\/wp-json\/wp\/v2\/posts\/357\/revisions\/400"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/projects.etc.cmu.edu\/expression\/wp-json\/wp\/v2\/media\/365"}],"wp:attachment":[{"href":"https:\/\/projects.etc.cmu.edu\/expression\/wp-json\/wp\/v2\/media?parent=357"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/projects.etc.cmu.edu\/expression\/wp-json\/wp\/v2\/categories?post=357"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/projects.etc.cmu.edu\/expression\/wp-json\/wp\/v2\/tags?post=357"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}