Tasks & Deadlines
### Task 1: Sign up to [webreg](https://www.ida.liu.se/webreg-beta/TDDD23-2022-1/The%20Course)
For registration of students and later grades in the course. Allwasy use this student_id in any communication with course staff. Signing up is individual. You later submit work together (if in a team) by adding all team_members student_ids in the file-name of any submissions.
### Task 2: Game Plan.
Specify the game project so that we can give you valuable feedback about scope and course criteria. Don't wait for feedback to get started, 99 out of 100 projects are fine from the start. Use [this Google Docs](https://docs.google.com/document/d/1J3qmErKulYqlx54U_yTaZbDfLOFXGtiBUwwr2PEGclM/edit?usp=sharing) as a starting point for you plan.
Deadline: *Sept. 9*
*Deliverable:* [Upload here, (sign in using your LiU account)](https://www.ida.liu.se/~TDDD23/upload).
### Task 3: Game seminar: Dates: *Sept 26, 27, 28, 29*
Sign up - **one person per team only** in webreg (https://www.ida.liu.se/webreg-beta/TDDD23-2022-1/Game%20Seminar).
We'll do max 8 projects per 2-hour session. Each project gets 10 minutes showing your game proejct status. Show live game and code - as real as you can. Avoid PPTs and plans, show things as they are. Note that student that have almost nothing here seldome finnish the course.
Booking through webreg will be announced.
### Task 4: Final Handin:
Hand in a Playable Game for mac or Windows for testing by course staff. Make sure your game is as clean and small as possible, excluding any non-used game assets you may have downloaded. If you are developing a mobile game, hand in a .apk-file for android so that we can test.
Deadline: *Oct. 25*
*Deliverable:* [Upload game here, (sign in using your LiU account)](https://www.ida.liu.se/~TDDD23/upload).
### Task 5: Game Teaser & Playthrough:
Do a 1-2 minute teaser screencast of the game. *One screencast per team* The more compact the better, especially for LiUGA where 30-60 seconds is the optimal format. Highlight the features of the game - showing its best sides. See old LiUGA screen-casts for inspiration. [Screen-cast recording software](http://en.wikipedia.org/wiki/List_of_screencasting_software).
Also, do a separate "full playthough" screencast that showcase the game. No time limit. This is not full, but showing different parts of the game that requires long playtimes to see. Here you make sure to show all the features of the game you want the examiner to see.
The teaser screencast will be used for the LiUGA competition (unless you specifically decline this). If you are choosen as a finalist, you have the chanse to update it, but you enter the competition with the teaser screencast handed in on the 28th. It has then to be publically accessible and a preferens tends to be youtube.
Also its recommended that you spend some time creating a high quality screen cast in terms of:
* video quality
* game play in focus (jurys picked youtube videos that show the game alot)
* action as fast as possible
* the fun illustrated through real game play
*Deadline:* Oct. 28*
*Deliverable:* [Submit link for Game Teaser and link to Playthrough screencast here](https://forms.gle/3UuTnmBnnA5oYDAi6)
### Task 6: Individual Development ScreenCast:
Do a 5-15 minute development screencast. *Every student does theri own screecast*. In this screencast you need to speek using your voice explaining the technical and design aspects of your game in relation to the examination critera of the course.
Also add a *game playthrough* of the game so that we can get a more full experience with your game from an experienced player (yourself) to see the full game. Its often impossible for us to play your game to the extent required to see all parts of the game.
Deadline: *Oct. 28*
*Deliverable:* [Submit link to individual screencast here](https://forms.gle/a7cwc8iyUsBR2nRB9)
### Late submission:
Late submission is made using the same handin forms but you should also *send an email to the examiner on December 10 or August 22* to annouce your late submission. Don't email in advance, e-mail on the date to avoid your submission getting missed.
Page responsible: Erik Berglund
Last updated: 2022-11-15