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

Computer Game Development and Design 2018/19 fall

  • Main
  • Lectures
    • Homework 1
    • Homework 2
    • Homework 3
  • Labs
    • Lab1 Introduction to Unity
    • Lab2 Unity Components
    • Lab3 & 4 Space Game
    • 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://goo.gl/forms/3fXfqCS6zukH3U5H3 (every team member has to do it!)

You must be logged in as a student of this course to choose the peer-review team

  1. The Game - Hannes Saariste, Karl Jaagup Kask, Mihhail Plohhotnitsenko
  2. DayDream - Siim Mardus, Kaarel Loide, Mihkel Pae, Karl Kuusik
  3. Vara de Mara - Helen Õunapuu, Rain Eric Haamer, Ott Adermann
  4. Brightdawn - Märt Mäemees, Mihkel Pent, Rimante Valancauskaite
  5. Reality Shift - Kirill Grjaznov, Aleksandr Titov, Aleksei Beljajev
  6. ShieldFormer - Eleriin Rein, Taavi Reisenbuk, Karl Erik Karandi
  7. Fishit - Ludvig Leis, Sten Teemant, Jaagup Russak
  8. Lost Cause - Tambet Uutsalu, Shivansh Ahuja, Samuel Rodriguez, Ott Saar
  9. Battleland - Kevin Ree, Janar Ojalaid, Oliver Ossip
  10. Fort Master - Meelis Perli, Einar Linde, Lauri Leiten
  11. Emission Impossible - Aron Eric Miljan, Jaanus Arukask, Michael Davõdovski
  12. Dungeon Raider - Kaarel Rüüsak, Karl-Walter Sillaots, Oliver Vinkel

Rules

  1. 3 students in a group
  2. No extensive violence or improper material
  3. Milestones with strict deadlines
  4. All team members have to come to the presentations
  5. Requirements are negotiable (but only before the deadline)
  6. -5 points for any requirement completely missing


Requirements

Design Document (01 October -> 5p):

  • Submission info: Design Document
  • Presentation

Milestone 1 (29 October -> 15p)

  • Project plan
  • UI Mockups + Scheme
  • Color Scheme description (Color palette)
  • Game Loop implementation (has one gameplay mechanic)
  • Win and Lose conditions implementation
  • Presentation (5 min per team)
    • You don’t have to prepare slides but you can. Cover following things:
    • 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 (26 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)
  • Upload your game build to your wiki page
  • 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) 18.01 (12.15 PM) Liivi 2-207 -> 25p

  • 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 (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);
    • 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