KIT109 Games Fundamentals Assignment 4 — Game Project Implementation Weighting: 20% Due Time/Date: 11:55pm Friday 16th of October (Week 13) Aims of the Assignment The purpose of this assignment is to give you experience at implementing a video game concept. It addresses the following ILOs from the unit handout: ILO2 apply knowledge of development principles and technical skills to develop games ILO3 identify and analyze user needs and take them into account in the design and implementation of games Assignment Requirements The assignment is to implement a 2D game prototype in Unity, along with some documentation showing the process undertaken to create your game. This is an individual assignment. Implementation Requirements Your implementation should provide a working game prototype with a welcome screen (i.e. a title with a “start game” button). You will be assessed on: The playability of your game. The ease of understanding of your controls. The stability/bugginess of your game. The coherence of the art style. The level of originality your game exhibits. Additional Features Additionally, you are required to address five of the following areas: Sound effects and background music. Custom, personally developed art assets: o Character art. o Background / Tilemap art. o Effects / particle art. o Title art. o UI art. User Interface (UI) functionality: o End of game screen with feedback on how well the player performed. o A restart game screen / button. o A help screen. o A settings screen. o A high‐score table. Local‐multiplayer controls Advanced programming functionality (these count as two areas each): o Artificial Intelligence (of e.g. enemies, NPCs, game world). o Path‐finding (of e.g. enemies, or NPCs). o Attract mode (i.e. the game should play itself like an arcade game to attract player’s attention). o Multiple levels / screens / a scrolling screen. To re‐iterate, implement five (or more, though only five are required) of the above features, here are two examples: Custom character art, custom title art, sound effects, end‐of‐game feedback, and a restart screen. Multiple levels (this counts as two), AI (this counts as two), and sound. Documentation This assignment also requires some supporting documentation which should be in the form of an itch.io DevLog that includes the following: A description of how well your final game compares to the vision laid out in your concept document. All differences should be listed and justified. A summary of the feedback gathered for each element that was tested for (as well as any observations that were made by you during testing), from your Week 12 Testing Session and a description of how each element’s feedback influenced your final submitted game. An asset list. This should list all the assets (or groups of assets) in your game and provide a description of the purpose/use of each. Any materials from other sources should be clearly identified and referenced in this section. A user guide containing the final name of your game, and a basic description of the gameplay and the controls. The user guide should also contain screenshots of each game screen and descriptions of each game function. o You may choose to include this as part of your game page on itch.io rather than in a separate DevLog. Referencing It is possible that you will use art assets and/or code from external sources in implementing your game. If so, you need to reference these as you would any other sources for written assignments. Any suitable referencing style is acceptable for this assignment, but it must at least be consistently and correctly applied throughout your document. See here for the University’s guide to referencing here: https://www.utas.edu.au/accounting‐communication‐ matters/writing‐an‐essay‐or‐report/referencing. Assignment Submission – itch.io Before 11:55pm Friday 16th of October (Week 13): Upload a WebGL build of your finished game to your existing itch.io project you created for Assignment 2 o Include on your game page: The basic controls (or entire user guide). A list of sources, if you’ve used art that you haven’t created yourself. A list of features, if you’ve attempted anything other than the basic version, detailing which features you’ve tried to create. Add a DevLog Post to your project titled “Documentation + User Guide” containing the information described above. Make sure your Game Project on itch has a representative thumbnail image, so that it looks nice in a collection of games সহ Assignment Submission – MyLO The following files must be submitted through MyLO before 11:55pm Friday 16th of October (Week 13): A zipped Windows build of the project. A .zip file of your entire Pong project. o It’s okay to delete the “Temp” and “Library” files from your zip if you want (but DO NOT delete the “Assets” or “ProjectSettings” folders). A signed individual assignment coversheet (available from the ICT website): https://secure.utas.edu.au/computing‐information‐systems/resources/cover‐sheets/Assignment‐Cover‐Sheet‐ Individual‐ICT.pdf o Have fun editing the PDF ͧͪͩͨ Assignment 4 — Game Project Implementation Individual Assignment (20%) criteria HD DN CR PP NN In your submission, you: In your submission, you: In your submission, you: In your submission, you: In your submission, you: ILO2 apply knowledge of development principles and technical skills to develop games Basic Content (25%) game has a title screen with a working start button game has a working start button game has no title screen or working start button game is highly playable and fun game is very playable game is playable game is somewhat playable game isn’t playable controls are very easy to understand and suit the game controls are easy to understand and mostly suit the game controls are easy to understand controls are somewhat easy to understand controls are hard to understand and/or don’t suit the game game has no (noticeable) bugs game has the occasional bug game has a few bugs game has some bugs game has many bugs art looks great, is very coherent, and suits the game art looks great, is coherent, and suits the game art is coherent and suits the game art is coherent art is a incoherent mess game is clearly highly original game is fairly original game is somewhat original game has one original thing game is a full clone ILO2 apply knowledge of development principles and technical skills to develop games Additional Areas (40%) address features from the following categories: sound; custom art assets: character art, background / tilemap art, effects / particle art, title art, or UI art; local multiplayer controls; User Interface: end of game screen, restart game screen, help screen, settings screen, or a high-score table; or advanced programming functionality (worth two): artificial intelligence, path-finding, attract mode, or multiple levels successfully address and well- integrate five features listed above successfully address five features listed above successfully address four features listed above successfully address three features listed abov
e address two or less features listed above ILO3 identify and analyze user needs and take them into account in the design and implementation of games Documentation (35%) provided a detailed list of differences from the concept document and thoroughly justified reasoning provided a detailed list of differences from the concept document and justified reasoning provided a detailed list of differences from the concept document provided a list of differences from the concept failed to provide a list of differences from the concept provided a summary of tester feedback and personal observations and gave a detailed description of how each influenced the game provided a summary of tester feedback and personal observations and gave a description of how each influenced the game provided a summary of tester feedback and personal observations provided a summary of tester feedback failed to provide a testing summary provided a complete list of assets (and identified the source of each) with a detailed description of the purpose/use of each provided a complete list of assets (and identified the source of each) with a description of the purpose/use of each provided a complete list of assets (and identified the source of each) provided a list of assets and identified the source of each failed to provide a list of assets and/or identify the source of each provided a user guide detailing the name of the game, and an easily understandable description of the gameplay and controls provided a user guide detailing the name of the game, and a basic description of the gameplay and controls provided a user guide detailing the name of the game, and a basic description of the gameplay and controls provided a user guide detailing the name of the game failed to provide a user guide detailing the name of the game provided a user guide containing easily understandable explanations of each game function and with relevant screenshots of each game screen provided a user guide containing explanations of each game function and with screenshots of each game screen provided a user guide containing explanations of each game function and with screenshots of some screens provided a user guide containing explanations of each game function failed to provide a user guide with screenshots and/or explanations of the game screens
