Institute of Computer Science
  1. Courses
  2. 2019/20 fall
  3. Computer Game Development and Design (MTAT.03.263)
ET
Log in

Computer Game Development and Design 2019/20 fall

  • Main
  • Lectures
    • Homework 1
    • Homework 2
    • Homework 3
  • Labs
    • Lab1 Introduction to Unity
    • Lab2 Space Game part 1
    • Lab3 Space Game part 2
    • Lab4 Unity Components
    • Lab5 Project Setup
    • Lab6 Tower Defence
    • Lab7 Tower Defence GUI & Buildings
    • Lab8 Tower Defence Content
    • Lab9 Blender Tree
    • Lab10 Sounds
    • Lab11 Animations
    • Lab12 Level Design
    • Lab13 Editor Extensions
    • Lab14 Lighting
    • Lab15 Procedural Generation
  • Projects
    • Design Document
  • Links

Projects

Teams

Please fill this form, I have to know your ÕIS username to give you an access to your wiki page! https://docs.google.com/forms/d/e/1FAIpQLScePmAm3lNz1lg6hR7znx6EVSRxVqLkdvXvtbFPmg3FDTf_bA/viewform?usp=sf_link (every team member has to do it!)

Peer-review spreadsheet: https://docs.google.com/spreadsheets/d/1EQVUi-82eKgBU8yUetsKLT-IcoPZ8MkVIgPOll7DtZ0/edit?usp=sharing

(write here which team you want to review, if this team has already been taken, pick another one).

  1. Hestia - Vladislav K, Stanisalv D, Kiryl L
  2. Graviform - Aap V, Marc D, Raul E K
  3. Slingshot - Mattias A, Rebekka B, Tanel M
  4. Forest throwdown - Erik T, Silver L, Hans H V
  5. Sanity Blade - Sander K, Kristofer K, Bogdan M
  6. Moving ON - Jon A, Kerstin Ä, Tasio
  7. After Annihilation - Paul P, Andri P
  8. Goalrunner - Rasmus M, Ingo I, Hendrik Š
  9. Brutheon - Marten M, Aleksander T, Allan M
  10. Afraid of the Dark - Oliver-Erik S, Marcus M, Karl M M
  11. Bossy Ozzy - Gromet S, Siim-Morten O, Cornelia T
  12. Awesome Robot Adventure - Kirill M, Martin N, Timo S
  13. Washed Ashore - Jaanus A, Sander S, Rander L

Rules

  1. 3 students in a group.
  2. No extensive violence or improper material.
  3. Each team has to give milestone presentations (at least 2 students present at the time).
  4. Two teammates have the right to give a penalty of 5 point to the third student for the last milestone if they find that the third student did not do enough work.
  5. The grading is subjective based on the requirements (both game design and implementation are graded).


Requirements

Design Document (01 October -> 5p):

  • Submission info: Design Document
  • Presentation

Milestone 1 (28 October -> 15p)

  • Itch.io page with downloadable link to the game.
  • Courses project page
  • Game Loop implementation (has one gameplay mechanic)
  • Win and Lose conditions implementation
  • Presentation (5 min per team)
    • Remind us about your game idea
    • Demo your game (live)
    • Tell about what went well and what went wrong
    • What are you going to change compared to your original idea

Milestone 2 (25 November -> 15p)

  • 5m gameplay
  • 5 gameplay elements
  • 2 units of scalable content (upgrades, items, enemies...)
  • First UI implemented (3 views)
  • First sounds implemented (5 sounds)
  • First level
  • First character partially animated
  • Pick a team to peer review (write their name to the spreadsheet)
  • Itch.io page has descriptions and pictures.
  • Presentation (5 min per team)
    • Demo your game (live)
    • Tell about what went well and what went wrong
    • What changes are you going to make

Milestone 3 (Final presentation) TBA -> 25p

  • Gameplay trailer on Ich.io (1-2 minutes)
  • 30m of meaningful gameplay
  • 10 gameplay elements
  • 20 units of scalable content (upgrades, items, enemies...)
  • Polished UI (partially animated & every action makes a sound)
  • Every interaction makes a sound
  • 2 characters animated
  • Has an in-game guide for all main features
  • Game has is understandable without the presence of developer
  • Game is playable from beginning to end
  • Peer review another team's game (the points will be added as a bonus)
    • Play their game
    • Write them feedback with about 5-10 suggestions on how to improve the gameplay. Publish it on your wiki.
  • Presentation (trailer video + 5 minutes per team + questions and discussion)
    • Introduce your team;
    • Describe your project idea;
    • Show a working demo about your project (can be a prerecorded video that is separate from your trailer);
    • Describe how the things turned out in your opinion and what are your future plans;
    • Make a conclusion;
  • Institute of Computer Science
  • Faculty of Science and Technology
  • University of Tartu
In case of technical problems or questions write to:

Contact the course organizers with the organizational and course content questions.
The proprietary copyrights of educational materials belong to the University of Tartu. The use of educational materials is permitted for the purposes and under the conditions provided for in the copyright law for the free use of a work. When using educational materials, the user is obligated to give credit to the author of the educational materials.
The use of educational materials for other purposes is allowed only with the prior written consent of the University of Tartu.
Terms of use for the Courses environment