We also took this experience to another school and had students play it. Despite a major bug in our assets, we had a chance to gather a lot of good feedback. For example, we noticed that high school students were using the automatic cooking how we expected but middle school students wouldn’t. We also had the chance to watch how a teacher would take his students through connecting our experience to their class. We got the chance to see how he could easily expand our experience and its lessons into further learning. For example, he would take his students through making the cheese pizza function then show how peperoni could be built up from that function. He would then try to get them to the point where they could see how they could make a pizza function with the ingredients as inputs. We are going to add connections like this into our lesson plans to help teachers realize these connections with their students.

Programming and art had to work to change the automatic cooking to match the new design. For art, this meant creating new cook-o-matic assets to represent what the new style of cooking is doing. This came in the form of machines that had openings you could place your made pizzas. For programming, this meant changing how we are handling automatic cooking to use the premade assets rather than then step style programming we had. This allowed us to better tie what a student is doing to what the machine is doing so they can understand the benefits.

Sound finished the first version of our tutorial and VO. This helps the player to get comfortable in the environment and understand what interactions are possible. It also introduces the players to the cook-o-matic and gets them to use it. We noticed that having that moment of introduction had a huge impact on how many players used the cook-o-matic.

One other change we made to the design was the introduction of a second oven. This oven would allow you to freeze a pizza rather than cook it. This gave us a simple way to expand the number of recipes while only needing small changes. For programming, this meant adding minimal tracking to the pizza to know if it’s hot or cold. For art, this meant just adding an extra layer to indicate if the pizza is frozen or not.

Programming worked this week to finalize the systems for both styles of cooking and the systems needed to support the game. In terms of cooking, the programming team finalized the systems that would build pizzas from the ingredients they are given. This meant that we could minimize our art assets and cooking possibilities so that there was little chance to go outside the expected bounds and break our systems. In terms of support systems, programming worked to build our basic feedback system of tips for orders and the system to accept pizzas for orders and send them to the customer.

Art worked to create the assets that worked with programming’s systems. This meant giving pizza assets that could easily have ingredients active or deactivated. It also meant making the assets that could easily be imported and layed out in Unity. Art also worked to try and get a final layout for the environment so that it was easy to explore and could feed into our design.

Design worked to simplify the scope and plan out the systems of feedback and progression. This meant ensuring that our design could easily be added in what we had while still achieving our learning goals. Design also need to work to figure out how we could build this experience and provide feedback to reinforce our learning goals. This meant planning out a level pattern that makes them want to use the cook-o-matic and realize its various benefits.

In terms of art and programing, we continued to push forward toward figuring out what might be possible for the MVP in 2 weeks. In terms of programming, this meant planning out how we can handle both the cook-o-matic and manual side of cooking. This includes planning what will happen if the recipe is wrong or in a correct order that is different than we planned. In terms of art, this meant exploring what space will work well in VR. This includes looking at whether a circular or square space will work best to make the user comfortable to explore and see all the information we need them to.

Design worked to finalize the idea and limit the possibilities in the design to make it easier on programming an art. This included balancing limited recipes while also not trying to favor cooking that might be liked by one group over another. We tried to address this by adding a second style of cooking but making each style only take about 5 steps. The new styles of cooking would be grilling and baking to try and keep it neutral.

Production worked to get the Halves presentation ready and to make sure everyone was practiced for the presentation. Production also worked to try and ensure that it was understood what the MVP should contain and when it needed to be done. This included working with all the other areas to figure out what was important and work with design to shrink the design to what is most important.