Week 13

The implementation process continued, as we worked on the last 2 quest of the game. Up to the end of this week, our implementation process has focused on the quests in their simplest state. These versions will assume the user does nothing but what they are told. It will then be necessary to insert several switches and triggers, so the game will provide the correct information at the appropriate time, etc.
It is possible that we underestimated the number of times we would need to iterate through the quests in this phase of our project. We found ourselves having to return to the first few quests for several reasons, such as...
1) We found a more efficient way of implementing a certain event.
2) To slightly altered part of the storyline, in order to fit the improved version
3) To add a switch or trigger that may have been overlooked through the first iteration

Because of this time consuming process, we were unable to tie everything together into one complete playable version. We examined our timeline that was created at the beginning of the summer, and discovered it to be slightly optimistic and perhaps slightly unrealistic with respects to implementation. We are now aware that, even with careful planning and design, more time should be allotted to the coding phase of a project such as this.

We also imported some scripts in hopes of making the educational information in our dialogue slightly more intriguing to the user. From our previous research, we found the text is less effective when it is just displayed all at once. The most effective way to make sure the user has absorbed the educational content in a text box (without using audio) is to have movement within that text box (text appearing letter by letter).