FIT2096 Game Programming 1 - Individual Assessment: MicroGame & Debugging Tasks
ASSIGNMENT 1 [20%] - Individual Assessment
MicroGame & Debugging Tasks
SUBMISSION DUE: Friday Week 04, 11:55 PM Covers Topics from Weeks 1 - 4
Late Penalty: 10% of total marks per day late
Learning Outcomes
Completion of this assignment demonstrates the following learning outcomes:
- Describe the geometric meaning behind vectors and matrices, and create code that
demonstrates how these can be applied practically in game programming, including for
object movement and collision
- 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 context, including basic movement and interaction
Brief
Across the first four weeks of semester you are expected to build a small microgame based on the lab tasks from weeks 2 - 4. 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 2 - 4
● Complete extension tasks for the lab exercises from week 3
● Maintain a git repository using GitLFS and weekly commits
● Debug and logging code for key variables
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 activities, you can of course seek assistance from your demonstrator, via the Ed forum or during consultations.
For the debugging tasks, you are required to add debug logging for each of the major functionalities created through the Week 2 and 3 labs.
The submission of this prototype must include the following components:
● Version Control via Git & GitLab
● Week 2 Lab Tasks
● Week 3 Lab Tasks
● Week 3 Extension Tasks
● Week 4 Debugging 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 serverThis 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
● DerivedDataCache ● 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 made weekly.
Week 2 Lab Tasks:
Suggested Completion Date: End of Week 2
As part of the assignment, you are required to complete the entirety of the guided Week 2 Lab, with emphasis on:
● Spaceship Creation
● Input Mapping/Actions
● Asteroid Collision
● Asteroid Spawning
More information on these tasks can be found in the Week 2 Lab.
Week 3 Lab Tasks:
Suggested Completion Date: End of Week 3
As part of the assignment, you are required to complete the entirety of the guided Week 3 Lab, with emphasis on:
● Spaceship Movement
● Spaceship Rotation
● Laser Spawning/Despawning
● Laser Collision
● Homing Asteroid Homing
● Homing Asteroid Spawning
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 assignment, you must also complete the extension tasks on the last page of the Week 3 Lab. This includes:
● Asteroids Explode into Precious Resources
● Orbiting Shield
● Space Station that Shoots Lasers
More information on these tasks can be found on the last page of the Week 3 Lab.
Week 4 Debugging Tasks:
Suggested Completion Date: End of Week 4
Completion of the additional debugging tasks on the last page of the Week 4 lab.
● Hitpoints
● Ship Collision
● Homing Asteroid Homing
● Player Controller Input
● Laser Collision and Despawning
● Asteroid Spawner
More information on these tasks can be found in the Week 4 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 2 Lab Tasks - 15 marks
○ Spaceship Creation
○ Input Mapping/Actions
○ Asteroid Collision
○ Asteroid Spawning
- ● Completion of Week 3 Lab Tasks - 25 marks
○ Spaceship Movement
○ Spaceship Rotation
○ Laser Spawning/Despawning
○ Laser Collision
○ Homing Asteroid Homing
○ Homing Asteroid Spawning
- ● Completion of Week 3 Extension Tasks - 35 marks
○ Asteroids Explode into Precious Resources
○ Orbiting Shield
○ Space Station that Shoots Lasers
- ● Completion of Week 4 Debugging Tasks - 15 marks
○ Hitpoints
○ Ship Collision
○ Homing Asteroid Homing
○ Player Controller Input
○ Laser Collision and Despawning
○ Asteroid Spawner
