During this bi-weekly report, I made my first significant contribution to the code base, which was both scary (with the freedom and ownership I was given) and satisfying when I eventually did a good job. I’m starting to truely feel like I’m a part of the WolverineSoft team, and am getting closer with my teammates in Programming and QA, which makes me happy?

These two weeks, I was assigned to rework the dialogue system, written by Samuel before me. A lot of back and forth communication was needed, as we were working on the same files, and sometimes changes got re-verted.

Week 3 Tasks Completed

• Playtested “Forest” scene again with one volunteer
  • Logged bugs and player confusion/sentiments with timestamps on Youtube in Confluence
  • Manually logged information to the Producer Feedback Tracker to ensure no duplicates
  • Prepared for Industry QA Playtest with Matt (by being extra diligent)
• Programming Task
  • Completed dialogue system activation, which people really liked! Now players have a choice in whether to start dialogue or not.
    • Done by adding new event listeners, instantiating pop-up indicators, and

Week 4 Tasks Completed

• No Playtests for this Week! Leo (QA Lead) told us to take a break for the upcoming spring break, and not work overtime.
• Dialogue System Rework
  • Rounding out the changes, created serialized field options to use the new system or the old system
    • This ensures that certain cutscenes are not manually activated, and players won’t miss essential cutscenes
    • This is where a lot of back & forth with Samuel came in, as some of my changes were overwritten and I wanted to learn from him

Hours Breakdown

• Studio Meetings: 4 hours + 30 minute overtime
• QA Playtests and Logging: 1.5 hours
• Programming Design Meetings: 30 minutes
• Programming + Debugging: 5 hours