Quack Attack

• Responsible for designing and planning 5 tutorial levels:
• Strengthened rapid prototyping skills from iterating in 1-2 week cycles.
• Investigated tutorial design/player onboarding methods and how a level designer might try to structure earlier levels to create an experience that is accessible to a wider range of players.
• Blocked out levels using sketches prior to implementation to facilitate design discussions with the team.
• Designed and scripted the camera to dynamically adjust its position and zoom level so players can see further ahead of themselves and better anticipate platform/enemy positions:
• Used ease-in and ease-out movements when panning and zooming camera to reduce motion sickness.
• Exposed all variables related to camera movement to the editor for easy modification.
• Helped run playtests, observing testers and compiling feedback/trends into documentation and playtest-specific spreadsheets for discussion with the team to drive the next iteration.
• Gained experience conducting playtests effectively through learning organisational methods, survey creation techniques, and feedback analysis strategies.
• Fine-tuned physics to give players more responsive, precise, and predictable control over their character.
• Designed character customisation system and implemented functionality via a "wardrobe" screen.
• Designed minimalist UI and customisation options to prevent choice paralysis.
• Contributed to, and maintained, design documentation and project artefacts.

• Led an interdisciplinary team of 4 using Agile principles and Scrum methodologies.
• Worked to ensure team members were doing okay mentally and physically throughout the weeks, reconsidering scope, project goals, and overall vision as needed.
• Maintained a 2-week sprint cycle with sprint planning and sprint progress/retrospective meetings held at the beginning and end of each sprint, respectively.
• Scheduled and coordinated team standups and check-ins with our primary stakeholder (aka our professor).
• Managed timeline/scope based on sprint deadlines and development goals by maintaining project Trello board.

• Designing levels that supported the goal of making onboarding accessible, and that showcased the game's mechanics and controls effectively.
• Coming up with a playtest strategy that allowed the team to get detailed feedback about areas in which the game could be improved, without resorting to creating an extensive survey.
• Promptly addressing burnout and production grind during times when classes and life got busy.

Rewarding Progression Through Unlockables

Locking cosmetic items in the wardrobe screen behind progression walls is one way to make progression meaningful and encourage players to keep going. Some cosmetic items could also be hidden away within secret or hard-to-reach locations in levels to reward exploration.

Further Polishing Camera Movement

The current camera system gives players better spatial perception, but it can still cause motion sickness in some people. Making the camera's panning smoother, or zooming out further to reduce the amount of panning required overall may fix this problem.

Addressing Difficulty Spikes in Tutorials

Some levels in the set of five tutorial levels were perceived to be more difficult than others during the most recent round of playtesting. Simplifying the layouts of these levels based on feedback will smooth out the learning curve, alongside conducting more playtesting as needed.