## News * **28/08/2026:** Course updated for 2026. * **Webreg Registration:** Register individually or in pairs via [Webreg](https://www.ida.liu.se/webreg-beta/TDDE20-2026-1/PRA1) if you will actively enrolled. * **Lecture:** September 9, 2026, 08:15, Room A302. ### Learning Goals * Develop proficiency in experience-oriented engines like Godot. * Plan, implement, and validate though tesing in group * Gain experience working within client-constrained specifications. * Apply scientific literature to practical software development. ### Other pages in the menu of concern. * **Game Theme** - Here the client requirements on your projects are described * **GIT Lab** - Here is how you set up and register your project repo for the course and where you version control the project * **MDA and PXI** - This is the development model you should maintain * **Game Feel** - Here is someting about. game fell that is mostly for the funal Astetics part of the MDA * **Tests** - here is how you can set up and manage tests in your Peer group for the evlauations your should do in accordance with the project schedule, see further down. ### Prerequisites Designed for senior students capable of independent work in new environments. Godot is the primary platform. * Proven experience in game, mobile, or web projects. * Ability to learn unfamiliar platforms quickly. * Understanding of interaction design principles. ## Course Content * Follow project models for experience-oriented software (games). * Work within client goals in combination with creative exploration * Ground design choices in scientific and/or industrial literature. * Evaluate end results using established scientific methods. * Conduct peer testing and provide structured feedback. * Make informed technical decisions, including responsible AI usage where results are validated and controlled. * Prioritize quality and polish over feature quantity. ## Development & Group Work * Work solo or in pairs on the game project. * Peer Teams are made from these, used for testing and feedback and potentially also for sharing discussions and help. Peer Teams will be added to a Teams chanel to be able to sync work better for testing meetings, chats, and online discussions. * Design follows the Mechanics, Dynamics, Aesthetics (MDA) framework. * Testing uses the Player Experience Inventory (PXI) - which is maped to MDA - via mixed methods (Likert scales and qualitative feedback). * Review feedback in person or via Teams. Optimally, testing in person give much more valuable observational feedback for seeing what testers do. But this is up to the group to determine. * Store all project data in your assigned Git repository. * Google Forms or other online tools or using itch.io for expopsing game and for data collection are allowed for data collection, but final data must be exported as Markdown (`.md`) files directly into the repository (raw CSVs or links alone are insufficient). ### Final Deliverables Store all items in the primary Git repository: * Playable Web build export. It may be pushed to closed testing on itch.io for conveniance, with the password and login features in the repo. Look at the test-page for some more details. Ensure that the playable builds are also ziped and placed in repo folders. * Gameplay screencast link in README (YouTube/OneDrive; no login required). * Codebase walkthrough screencast link in README. * Summary report, in Markdown format, detailing feedback received and resulting changes. ## AI Policy AI tools are permitted for prototyping and implementation, subject to the following terms: * You are fully responsible for architecture, readability, and correctness. * Replace sub-optimal AI defaults with native Godot nodes and structures. * Refactor generated code to avoid bloat and maintainability issues. * Unexplained AI code will lead to a failing grade. The technical screencast must prove full code comprehension. * AI usage is optional, but declaring your AI usage status (including zero usage) in your repository is mandatory. ## Project Schedule - **Week 37:** Concept design, scope definition, storyboarding, paper prototyping. - **Week 38:** Pitch mechanics within peer Groups. (Base Mechanics in MDA) - **Weeks 39 to 42:** Functional implementation (Functional Dynamics in MDA - PXI Level 1). - **Week 43 (Mon):** First peer Test (PXI testing, feedback collection, calrifying discussion and observation). - **Weeks 45 to 50:** Polish, visual feedback, game feel. (Aesthetic Emergence in MDA - PXI Level 2) 2. **Week 47:** Second peer Test, with clarifying discussions hosted. (PXI testing ... ) 1. **Week 50:** Final peer Test on final builds, with clarifying discussions hosted. (PXI testing ... ) ## Submissions Upload source code, README screencast links, and Markdown reports to GitLab. * **Option 1:** December 16 * **Option 2:** January 14 ## Technical Platform & Scope * **Engine:** Godot Engine (Open Source). * **Primary Target:** Playable (Web/Compatibility renderer) for closed testing via itch.io. Use password and share on the git repo and teasm. All playable version should remain for the final examination. --- ## Course Evaluation (Past Results) * 2025 : 2.00 (1 student) * 2024 : 2.50 (two students: 4, 1) * 2023 : 5.0 (one student) * 2022 : 4.0 * 2021 : 4.5 * 2020 : 2.75 * 2019 : 4.0