Tasks & Deadlines
### Task 1: Sign up to [webreg](https://www.ida.liu.se/webreg-beta/TDDD23-2024-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 30, October 1, 2, 3*
Sign up - **only one person per team signs up** [in webreg](#)
We'll do max 8 projects per 2-hour session. Each project gets 10 minutes showing your game project status. Show live game - as real as you can. Avoid PPTs and plans, show things as they are. Note that students that have almost nothing here seldom finnish the course.
Booking through webreg - TBA.
### Task 4: Game Teaser & Playthrough:
Ever team does **1 teaser video** and **1 playthrough screncast** video together.
Teaser: a 1-2 minute screencast highlighting the best aspects of tha game. The more compact the better, especially for LiUGA where 30-60 seconds is the optimal format. Highlight features of the game, show real game content (please don't waste presious seconds on long intros with mystic messages that really shows ...nothing). See old LiUGA screen-casts for inspiration, in particular finalists. [Screen-cast recording software](http://en.wikipedia.org/wiki/List_of_screencasting_software).
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 chance to update, but you enter the competition with the teaser screencast handed in on the 28th. The screencast should be publically and easilly accessible - a preferens tends to be youtube.
Also its recommended that you achive:
* 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
Playthough: A screencast that showcase the game. No time limit. This need not be a full play-through - your game may never end - but is should show the games entire content.
*Deadline:* Oct. 28*
*Deliverable:* [Submit link for Game Teaser and link to Playthrough screencast here](https://forms.gle/CBywQ2yG1LeyYbvf8)
### Task 5: Individual Development Screencast:
Every student does their own 5-15 minute development screencast. In this screencast you need to **speek using your voice, recorde both your face and your desktop using PIP or Picture-in picture. when demonstrating** to explaing the technical and design aspects of your game in relation to the examination critera of the course concreatly showing your development enviroment, presenting settings, code or other aspects.
Yu need to google how to set up a PIP-recording using your prefered software. You can use Teams meetings that you record. Also, OBS-software is great for such recordings and for instance in QuickTime on Mac you starting a MovieRecording from your camera, make sure it floats on top, and then start a screencast-recording ontop of that. Youtube how to do it :=)
Deadline: *Oct. 28*
*Deliverable:* [Submit link to individual screencast here](https://forms.gle/VfwveFKVbjYYzP9p6)
### Late submission:
Late submission is made by adding all your data to the formes used on the normal submissions, but also sending a and 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 getting missed. You of course, still should do the same 3 screencasts as for a normal submission. Participation in LiUGA is of course not possible even though we are reusing the same forms.
Page responsible: Erik Berglund
Last updated: 2024-12-11