As our groups Mechanics Designer (Aysa) was absent during Week 1, I had to fill in the role and make a start on the Player. However, once Aysa had returned we had asked her to take over with the Player.
For Week 2, we had tasked Aysa with creating a dash mechanic, a vital part of the player controller. After she implemented the dash into the project, I then showed her how to commit it into the repository for Lament (shown in other post). Which then allowed me to pull the latest commit and see the dash for myself, then I told Aysa my opinions about the dash:
As the more experienced and capable coder within my group, I often found myself giving advice to our Mechanics Designer about scripts and general Unity issues.
In this instance I gave her a general idea on how I would approach the issue, and also providing further resources to help her to fix the issue.
Unfortunately, at this point in the project, my main focus was on creating the Procedural Room Generation, so I was unable to get to fixing the dash this week.
Interdisciplinary Collaboration
As the Technical Designer, it was up to me to help our designers understand how the animations would work practically in unity (and vice-versa). This helped our Mechanics Designer begin developing the player further.
Helping with programming
As the lead programmer, group members will come to me with questions about C# script writing in unity, especially our Mechanics Designer, Ayse:
