FIT2096 - Games Programming
ASSIGNMENT 1 [15%] - Individual Assessment
MicroGame & Debugging Tasks
SUBMISSION DUE: Friday Week 05 11:55pm
Covers Topics from Weeks 1 - 5
Late Penalty: 5% of total marks per day late
Learning Outcomes
Completion of this assignment demonstrates the following learning outcomes:
1. Describe the geometric meaning behind vectors and matrices9 and create code that
demonstrates how these can be applied practically in game programming9 including for object movement and collision
2. Create game programs that demonstrate an understanding of the programming game loop and how to set it up
4. Create game programs that demonstrate an understanding of physics in the games programming context9 including basic movement and interaction
Brief
Across the first five weeks of semester you are expected to build a small microgame based on the lab tasks from weeks 1 - 5. This includes the main set of tasks as well as extension tasks outlined in the weekly lab notes.
This assessment involves the following:
● Follow and complete the guided lab exercise from weeks 1 - 5
● Complete extension tasks for the lab exercises from week 2 - 4
● Maintain a git repository using GitLFS and weekly commits
● Debug and logging code for key variables
Submission Requirements
Upload the link to your Faculty GitLab repository via Moodle. You will be assessed based on your most recent commit prior to the due date.
Task: MicroGame and Debugging
The main lab tasks each week are structured as a step-by-step guide to assist in their completion. The extension tasks are provided with an overview of the task to be completed with general pointers and information to get you started on the right track.
The extension tasks are intended to be more difficult and require some enquiry and initiative from your part. If you get stuck on the extension activities9 you can of course seek assistance from your demonstrator9 via the Ed forum or during consultations.
For the debugging tasks9 you are required to add debug logging for each of the major functionalities created through the Week 29 3 and 4 labs.
The submission of this prototype must include the following components:
● Version Control via Git & GitLab
● Week 1 Lab Tasks
● Week 2 Lab Tasks
● Week 2 Extension Tasks
● Week 3 Lab Tasks
● Week 3 Extension Tasks
● Week 4 Lab Tasks
● Week 4 Extension Tasks
● Week 5 Lab Tasks
Version Control via Git & GitLab:
Suggested Completion Date: End of Week 1
When building your prototype you must store your work within a Git Repository using the Monash FIT GitLab server (https://git.infotech.monash.edu).
This repository should use GitLFS for all files within the Content folder (game assets).
GitIgnore File
The repository must use a .gitignore file to exclude the following folders from the repository:
● .vs
● Binaries
● Build
● Derived DataCache
● Intermediate
● Saved
Instructions for setting up this repository can be found in the week 1 lab tasks on Moodle. Additional material is also available in the software installation guide under week 1.
Commits to the repository are to be at least once a week.
Week 1 Lab Tasks:
Suggested Completion Date: End of Week 1
As part of the assignment9 you are required to complete the entirety of the guided Week 1 Lab9 with emphasis on:
● Creating Items
● Viewing Items in the Inventory UI
● Deleting Items from the Inventory UI
More information on these tasks can be found in the Week 1 Lab.
Week 2 Lab Tasks:
Suggested Completion Date: End of Week 2
As part of the assignment9 you are required to complete the entirety of the guided Week 2 Lab9 with emphasis on:
● Creating a Pawn
● Creating a PlayerController
● Creating Actor Components
● Creating user inputs
● Creating power ups
More information on these tasks can be found in the Week 2 Lab.
Week 2 Extension Tasks:
Suggested Completion Date: End of Week 2
As part of the assignment9 you must also complete the extension tasks on the last page of the Week 2 Lab. This includes:
● Creating a shrink ability
More information on these tasks can be found on the last page of the Week 2 Lab.
Week 3 Lab Tasks:
Suggested Completion Date: End of Week 3
As part of the assignment9 you are required to complete the entirety of the guided Week 3 Lab9 with emphasis on:
● Creating interactable objects
● Creating moving enemies
● Creating hazards
More information on these tasks can be found in the Week 3 Lab.
Week 3 Extension Tasks:
Suggested Completion Date: End of Week 3
As part of the assignment9 you must also complete the extension tasks on the last page of the Week 3 Lab. This includes:
● Creating complex moving enemies
More information on these tasks can be found on the last page of the Week 3 Lab.
Week 4 Lab Tasks:
Suggested Completion Date: End of Week 4
As part of the assignment9 you are required to complete the entirety of the guided Week 4 Lab9 with emphasis on:
● Creating additional hazards
● Spawning enemies at run time
● Working with stationary and orbiting rotations
More information on these tasks can be found in the Week 4 Lab.
Week 4 Extension Tasks:
Suggested Completion Date: End of Week 4
As part of the assignment9 you must also complete the extension tasks on the last page of the Week 4 Lab. This includes:
● Creating shields
More information on these tasks can be found on the last page of the Week 4 Lab.
Week 5 Debugging Tasks:
Suggested Completion Date: End of Week 5
Completion of the debugging tasks in the Week 5 lab.
● Custom logging profiles
● Logging key information of mechanics
More information on these tasks can be found in the Week 5 Lab.
Assessment Criteria
Your assignment will be marked on the following criteria listed below.
● Git Repository Setup - 10 marks
。 Setup of git repository with GitLFS and gitignore being utilised
● Completion of Week 1 Lab Tasks - 5 marks
。 Creating Item Class
。 Adding Item Deletion
● Completion of Week 2 Lab Tasks - 10 marks
。 Creating Actor Components
。 Creating additional user inputs
。 Creating power ups
● Completion of Week 2 Extension Tasks - 10 marks
。 Giving the pawn the ability to shrink and scale up
● Completion of Week 3 Lab Tasks - 10 marks
。 Creating interactable objects
。 Creating moving enemies
。 Creating hazards
● Completion of Week 3 Extension Tasks - 15 marks
。 Creating complex moving objects
● Completion of Week 4 Lab Tasks - 10 marks
。 Creating additional hazards
。 Spawning enemies at run time
。 Working with stationary and orbiting rotations
● Completion of Week 4 Extension Tasks - 20 marks
。 Creating shields
● Completion of Week 5 Debugging Tasks - 10 marks
。 Custom logging profiles
。 Logging key information of mechanics A detailed marking rubric is provided on Moodle.
Feedback Information
You will receive a mix of formal and informal feedback for this assessment. Demonstrators will provide feedback in your scheduled lab sessions informally the week after submission. Formal feedback will be provided within 10 business days of submission.