A Unity Music Game
Rizu: Stage!
Rizu: Stage! is a 2D rhythm dungeon crawler for Android tablet where you move and attack on the beat. Help intergalactic idol Rizu explore 6 different venues, reclaim her microphone, and get back to the stage to perform. Enjoy the game’s adorable hand-drawn anime art style, bubbly music, and six levels. Kill enemy haters that get in your way, rack up a high multiplier and higher score, and go for the best rank for each level.
Game Trailer
Design
This is the first level of the game, where the most basic mechanics are taught to the player. The player is guided to learn movement at the initial stage, followed by learning how to pick up items, defeat monsters, and take down multiple enemies. Gradually, the player will learn to master timing, and at the end of the level, the mechanic of picking up the microphone and returning to the stage is introduced.
This is the second level of the game, where the player's understanding of the core mechanics is further reinforced and expanded. The level begins by introducing environmental hazards that require precise movement and timing to overcome. The player will then face enemies with new attack patterns, encouraging strategic use of previously learned combat skills.
This is the fourth level of the game, where the player’s skills are tested in more complex and dynamic scenarios. The level emphasizes rhythm and flow, requiring the player to chain together movement, combat, and dodge mechanics seamlessly. Enemies now appear in coordinated groups, forcing the player to prioritize threats and manage space efficiently.
This is the final boss level of the game, where all previously learned mechanics are pushed to their limits. The player enters a high-stakes arena and must face the ultimate enemy in multiple phases, each introducing new patterns, mechanics, and environmental challenges. Mastery of movement, timing, combat, and dodge is essential, as the boss adapts and escalates its attacks with each stage.
What Went Well?
1. I believe our team demonstrated exceptional efficiency throughout the project. During work phases, we maintained a strong focus on our individual tasks, avoiding unnecessary discussions or distractions. When challenges arose, we quickly collaborated to address issues and promptly returned to our respective responsibilities. This balance of independence and teamwork significantly enhanced our productivity.
2. Our team excelled in conducting highly efficient and productive discussions. Whenever we encountered issues, we proactively and promptly raised them, engaging in meaningful dialogue about whether a particular design or game objective should be maintained. During these discussions, we remained focused on the primary goals without straying into unrelated topics. If the conversation veered off track, someone would always step in to redirect the group back to the main point. As a result, every discussion was purposeful and concluded swiftly and effectively.
3. Our team demonstrated exceptional adaptability and responsiveness throughout the project. When faced with unexpected challenges or feedback, we were quick to assess the situation, pivot our plans if necessary, and implement solutions efficiently. This flexibility ensured continuous progress without compromising the quality of our game, allowing us to address issues constructively and meet our goals within tight timelines.
What Went Wrong?
1. During the early stages of development, we were heavily focused on rapid iteration, which led to significant daily changes in various aspects of the game. However, we overlooked an essential element: maintaining consistent communication with our stakeholders. We failed to provide timely updates about the new changes we were implementing and instead relied solely on our own judgment to make adjustments. This lack of stakeholder involvement resulted in misaligned expectations and missed opportunities for valuable feedback.
2. We did not effectively utilize the task board to select and prioritize our tasks. Instead, we tended to start working on tasks we found personally interesting. This approach introduced unnecessary risks. Firstly, there were times when we forgot about certain tasks entirely, only to realize them later when there was no time left to complete them. Additionally, we often underestimated the time required for specific tasks, which led to situations where critical tasks were left unfinished as deadlines approached.
3. With each iteration of our game and the introduction of new versions, we failed to compare them with previous builds. This oversight led to the unintentional loss of content that existed in earlier versions, which was directly omitted in the latest updates. To address this, we should have conducted a comparison after completing each milestone build to evaluate which issues were resolved and identify content worth retaining. This would have allowed us to carry those elements forward into the next milestone effectively.
What I Learned?
1. During this TGP, I learned how to communicate effectively with my team members. I discovered the importance of being a collaborative team member, maintaining clear and constructive communication, and building strong relationships to ensure smooth teamwork. Prior to this project, my experience was limited to individual projects, so this was a completely new process for me. I’ve now gained valuable insights into creating a game as part of a team, which has been a transformative experience.
2. I learned the importance of planning, particularly in setting milestones and deadlines. The initial planning at the start of each milestone is crucial as it determines the amount of work we accomplish within a week. Regular check-ins proved to be highly effective in ensuring timely progress and successful iterations throughout the project.
I learned how to define a game and navigate the iteration process. At the beginning, we would brainstorm ideas and work on breaking down the various elements of the game. We categorized them into broader objectives and further divided them into smaller, manageable tasks. This approach was crucial in clarifying the project's goals and ensuring that everyone had a clear understanding of their responsibilities