Game Design II
course task vaults
- form a team
Week 2:
- establish a documentation - share a link
- think about your game design theory presentation
Week 3:
- Sign Up Your Team - fill the spreadsheet with all the info mentioned in the column headers. Same as last semester.
- GDProposal - describe your team project (game design idea or game design proposal or game design document) - you can use templates form last course. The document must contain understandable description of your project aka "the gist of it". Use your experience to be as brief and as informative as you can. No marketing sauce this time. Only game design.
Week 4:
- share a link with your game design documentation into a course spreadsheet - ideally a wiki / confluence / git documentation...
Week 5, 6, 7:
- prepare presentations:
- Prepare the game project presentation. Bring the build / printed version of the game. There will be a 10 minute presentation of your project and 15 minute discussion. While preparing the presentation (I recommend google presentations), focus on game design bits you would like to do this semester in detail. If possible, try to formulate a game design theory bit that is relevant and include readable / watchable sources in the presentation. All team members should be present.
- sign up for the presentation:
Week 7:
- Report the progress on the game, include link to documentation. Few sentences, few bullet points, nothing fancy or robust.
Week 8:
- Prepare the game for public test on the course.
- Report the progress on the game, include link to documentation. -> HERE
Week 9:
- Report the progress on the game, include link to documentation. -> HERE
Week 10:
- Report the progress on the game, include link to documentation. -> HERE
Week 11:
- Report the progress on the game, include link to documentation. -> HERE
Week 12:
- Report the progress on the game, include link to documentation. -> HERE
Week 13:
- Report the progress on the game, include link to documentation. -> HERE
Week 14:
- Report the progress on the game, include link to documentation. -> HERE