This week the team established more specific criteria outlining our idea’s design, while still focusing on implementation that will take us to our first prototype.
The team met throughout the week to discuss and clarify specific elements of our approach, such as map structure and player data.
At the beginning of the week James worked with the team to break out user stories from our discussion so far, and then prioritize specific tasks. Throughout the rest of the week, he worked with the technical staff to set up Hansoft for project management and coordinated with the client regarding playtest releases and obtaining their updated educational standards.
Christian outlined the design for our player’s digital field notebook along with a rough mockup for it’s general layout and discussed it with the team. Later in the week he used the Google Maps client to examine the terrain of the arctic tundra, and collaborated with Eric (the artist who will eventually make the game’s terrain) on our desired criteria before pulling out sections and making rough overlays of the features for reference.
For the artists, Eric completed the caribou model at the beginning of the week and then handed it off to Shashank who spent the week working on tailoring his previous skeleton to a realistic rig for the animal. Meanwhile, Eric moved on to work diligently poster and branding in order to complete it by the deadline. By the end of the week, Eric designed the team’s logo ( a Yeti’s face) and was putting the finishing touches on the poster featuring a kindly Yeti beckoning the viewer to join him in exploring the tundra.
For programming, Ken divided his efforts between continued work on the player controller, specifically allowing the user to switch between inputs, and incorporating the Unity 4.6 UI tools. Levi spent his time planning out implementation of the server component and database structure.
With the 1/4s walkaround approaching at the end of next week, the team plans to compile what we have completed so far into a prototype with basic functionality to receive faculty feedback and to test our own assumptions.