Devlog 2.2: Production

Despite the aforementioned turmoil of losing our main programmer, the team has overall found success during production. No doubt, it started small, our implementations were minor and we had only begun dipping our toes into the first couple of weeks of the semester. Initially, we were able to follow our plan through the cards that had been added to our Trello and fell into a routine. 

The team is closer than ever as we find time to work on the game together outside of class. Overall, we are very accommodating to each other’s needs and schedules and tend to work around other courses rather swiftly. We find there are times we work best when in the same room as we are able to provide feedback to each other and work accordingly. 

There has definitely been a lesser success in production near the end of the first half of this semester as the team began feeling the weight of another year coming to a close end. From the first playtest and the weeks of production, the team found that we had scaled our game to an almost unobtainable extent. Despite this, we were able to overcome and carry out our second round of playtesting with a proper build that considered the feedback of the first. That being said, our second playtest introduced us to an equal number of flaws that were apparent in the first. 

Due to this, the team readily decided we would be able to risk cutting portions of the game to better fit our schedule in order to handle both changes . These feature changes include: 12 weeks of gameplay moved to 3-6 weeks, the narrative takes the forefront, and cutting out the third mini-game planned in the GDD.