Design Document

This is the game design document, as part of the game jam submission. It shows that the scope was actually reasonable for 2 weeks, and that I did not keep up with updating the document as I completed parts of the game. Despite that, writing the document solidified the scope, features, and limitations of the game in my mind as I worked on it. It was particularly useful to define the small deliverables in the part at the end. Next time I will try to keep up with updating the document as I complete parts of the game, but even just as it was writing the document was certainly not a wasted effort. It also lets me reflect now on how my time estimates lined up with the real time cost of working on each asset or partial deliverable. More than I thought. 

I rewrote the movement script so many times, I don't know how it works properly. Is programming games always this way? 

Here is the Google Drive link: https://drive.google.com/file/d/1N8gZBRv5qPSKut6pYoibzDGxj8DVBhKy/view?usp=shari...