ITECH2001 Game Development Fundamentals Assessment

Your task this semester will be to first pitch, then plan and create assets for, and finally develop a small video game prototype. Your game must not be based on any existing artistic works or media, such as film, television, games, stories, or characters. It must be your own original creation based on a provided randomly generated Scenario.

This task is split into three manageable assessments and described below in more detail. After reading the specifications, and learning through lectures and labs, if you are still unsure of the complexity required for your final game prototype, ask your lecturer or tutor, and look at previous student submissions from past semesters in the “Previous Student Examples” located in the Assessments section of Moodle.

Part A: Game Pitch and Peer Feedback (10 marks)

Your task for Part A of this Assignment is to:

• Pitch a new video game concept based on your generated Scenario in a short, recorded video.
• Provide constructive peer feedback to another student regarding their

Game Pitch Video (7 marks)

Using your provided Scenario that has been randomly generated specifically for you, your first task is to think of a new game idea that fits the variables of your scenario, then pitch your game idea in a recorded video. The full details of what to do for this pitch are outlined below:

• Your game pitch will form the early concepts for the game prototype level/scene you will be planning in Part B, and then developing in Part C. Therefore, read over Part B and Part C below to gain a full understanding of the game prototype you must plan and then later develop into the small
  • You should start your planning document for Part B early in the semester and have a good idea of what your game will be This will help you immensely for this Game Pitch.
• A game pitch in industry is used to try to sell your game concept to a potential investor and their market, or directly to the gaming target audience via crowdfunding; you want to them to fund your game!
  • Imagine you only have 2 minutes time to describe your game concept to a game publisher! Therefore, it should be short, interesting and informative!
• Read these instructions thoroughly and think carefully about your

o Your game pitch will be a recorded video presentation. Have fun with it! It is about games.

• It must meet the criteria and be between 1:30 to 2 minutes in length.
• It can be recorded and edited any way you like, but you must be identifiable at the start of the video, and be talking throughout to explain your game concept.
• If recorded on a mobile device, it must be in landscape view à

and must be clear in video and audio.

Write a transcript of what you are going to say in the video. In the written transcript, include:

• A screenshot of your randomly generated Scenario. There are penalties for not following your scenario.
• A high concept statement of your game idea. Use this to introduce your game idea during your
  • This is a concise but informative description of your game concept. A few sentences (~one paragraph) are used to summarise your game in an exciting manner – sometimes called an “Elevator Pitch” – a short and persuasive pitch that quickly defines the value and excitement in your
  • Try to include as many of the most important details as possible, briefly summarised into a one paragraph high concept statement (Lecture 2 explains high concept statements, with a few examples), including:
    • The Game Title
    • Genre (see lecture 1)
    • Player control such as player viewpoint, and game engine used
    • General Story/Setting and major Characters/Objects (see lecture 3 and 4)
    • Important game Mechanics, including the major goal (see lecture 4)

o Make sure it is clear (for the marker) when your high concept statement begins and ends.

• After your initial high concept statement, provide some expanded details such as the most interesting features of your future game
• During your pitch, in both the high concept statement and expanded details, you must back up your discussion with supporting materials:
  • Supporting materials can be anything that helps you to describe your game quickly:
    • Examples: Sketches, images and/or videos
      • Characters, objects, diagrams, ideas, game mechanics, and/or
      • They could be your own, or examples from similar games that inspire
    • Supporting materials can be shown:
      • In person during your pitch (record them clearly on the camera).

§ Edited into the pitch using any video editing software.

Peer Feedback (3 marks)

The second task of Part A requires you to watch other students’ game pitches and provide some constructive feedback to one other student to help them improve their designs for Part B.

After posting your own video of your game pitch (see below on how to submit):

• Read the titles of other students’ game concepts and view some game pitch videos that appeal to
  • If not many are available after you have submitted, wait a little closer to submission deadline for more to be uploaded (but don't forget about this!)
• When you discover an interesting game concept among your peers, reply to their forum post and provide polite and constructive feedback such as:
  • Evaluating their high concept statement and reflect on methods to improve it for Part B planning
  • Providing advice on they could better meet the overall game prototype specifications on page
  • Suggesting forms of media and similar games that may assist them to explain their game
  • Addressing the energy and excitement from the
• The goal is to provide constructive feedback on how they could improve their game concept when they work on Part B and eventually Part C, while still meeting the criteria of

For all forums remember:

• Text based communication can be misinterpreted (eg: Sarcasm and humour is not always obvious).
• Please obey discussion forum Do not use the Moodle forums inappropriately.

Part B: Prototype Plan and Assets (25 marks)

Your task for Part B of this Assignment is to

• Document a prototype plan that outlines the design for your game prototype based on your generated Scenario, and
• Create three artistic assets based on your generated Scenario for your game

Prototype Plan (15 marks)

You should begin working on this assessment when the course commences, with a solid plan for your game prototype, this will help you to create your Pitch more easily.

Remember, this planning document is about making plans for just the game prototype you will develop in Part C, it is not a full game design document, but rather the design of a single level or area intended for your prototype using your provided Scenario that has been randomly generated specifically for you.

This prototype planning document does not have a word count requirement, but

• Expect to write more than 1500 words to address all of the criteria outlined further
• Include lots of images to support your designs and make it easier to understand!
• Your planning document should be easy to understand, visualise, and be detailed enough to develop a prototype for your game without any

The following areas should be addressed in your prototype plan document:

1. Generated Scenario (review your generated Scenario in Moodle)
   • A screenshot of your randomly generated There are penalties for not following your scenario.
     • The penalty is much more severe in Part B and C, as you have had time to fix issues since Part

1. High Concept Statement (see lecture 2)
   • This is similar to the high concept statement provided in your Game Pitch, but now you have a chance to follow up on any feedback and improve it! If you have made any major changes since your pitch (or were requested to change something in your Part A feedback), make sure the high concept statement reflects
   • Once again, try to include as many of the most important details as possible, briefly summarised into a one paragraph high concept statement, including:
     • The Game Title
     • Genre (see lecture 1)
     • Player control such as player viewpoint, and game engine used
     • General Story/Concept and major Characters/Objects (see lecture 3 and 4)
     • Important game Mechanics, including the major goal (see lecture 4)
     • World/Setting (see lecture 5)

2. Mechanics (see lecture 4)
   • Every student will have game mechanics to discuss that emphasises exactly how your prototype will With the main concepts summarised through the high concept statement, this section requires detailed explanations of your mechanics for the game prototype scene you will build.

o There should be thorough discussions of each of these aspects from the lecture:

• Space - This should address the space that the prototype level/scene will be played within, focusing on the dimension, movement, and Environment is to be discussed in another section.
• Time - This should address any conditions that affect the timing in the prototype level/scene. Discussion should include how time affects actions, gameplay, player control, and
• Objects - This should be a comprehensive list of all objects including their usage, purpose and states that will be needed in the prototype level/scene, and can include characters/enemies (lecture 3), props, cameras, lights and other objects.
• Actions - This section requires basic actions and possible strategic actions conducted by the player in the prototype level/scene, as well as the keyboard/mouse input required to conduct the actions. For the complexity of this course, movement and 1 or 2 additional basic actions is usually
• Rules - This section requires the rules of the prototype level/scene: object interaction, action usage, end condition(s) - win, loss, and/or prototype completion, as well as scoring, etc. Include any chance elements here that may create randomness and uncertainty for the player, and/or alter the

• Include images/diagrams to help support your descriptions of

3. World / Setting (see lecture 5)
   • A 3D game will require some sort of world, environment, or setting – even if it is
   • Your randomly generated Scenario will provide you with a broad environment type. You should expand on this to provide detail and can consider the following when documenting your designs:
     • Is it indoors, outdoors, more surreal, abstract, ? What does it look like?
     • Does it draw influences from any culture, atmosphere or setting?
     • What year is it based in? Is it fictional, historical, contemporary, fantasy, ?
   • Include images/diagrams to help support your

4. Level Design (see lecture 5)
   • It is important that you thoroughly plan the level or contained area/scene that you will develop for your Part C playable game You must include the following:
   • Complete level/scene map – Draw a detailed top-down map of your proposed level/scene(s) for the game prototype, to act as a blueprint for the development
     • You can use software to design your map, or hand draw the map and scan it or take a CLEAR photo
     • Map must be created by yourself, or you will lose
     • The map must indicate locations of the following:

· Player start location

• All Triggers/Events
  • Including the dialogue event and multiple events assigned to you in your randomly generated Scenario as well as an ending condition to win the

· All Characters/Enemies/Props/Objects

• All objects (including characters, enemies, props and other objects) from the Object list indicated in section 2 Mechanics should be shown on your map

· The optimal Player progression through the map to win / finish the prototype

• Discussion about the triggers/events with pseudocode, relating it back to your completed
  • Identify and summarise how each event will be triggered that was indicated on your
    • (for more details about triggers and events, see Part C). Also Discuss:

• Are certain actions required by the player to trigger an event?
• What is/are the end condition(s)? How does the player win, lose, and/or complete the prototype?

• Provide simple pseudocode to design the process of each

• (Events, Triggers and Pseudocode are first introduced in Lecture 6, but you should view Part C to see the requirements of Events and Triggers in the )

Asset Creation (10 marks)

It is expected that you can develop your own 2D and 3D art assets that are appropriate for your game prototype. All students are required to develop at least three assets (not just primitive shapes or basic artwork) created by yourself in 2D (materials), and 3D (meshes). When you work on the game prototype development in Part C of this assignment, you will use your three (or more) self-created assets, as well as free downloadable Unity store assets.

The following identifies the specifications for creating your own art assets:

• GIMP Asset (see lab 1)
  • Every student must create one 2D asset using GIMP. Your generated Scenario will indicate to create a texture for your randomly assigned
  • For higher marks, also create a normal map (see lab 1) for your
  • Save as a .XCF file type AND export to PNG for submission
• Blender Assets (see labs 2 and 3)
  • Every student must create two unique 3D assets using Blender. Your generated Scenario randomly assigns one model, and gives you creative freedom to decide on the second model you want to
    • These models will be Static 3D models/meshes that will be used as props in your prototype

Do not create animated, humanoid or animal models (this is too difficult and time consuming).

• Save as a .blend file type AND export to FBX for submission

· ALL Assets created following the lab exercises do not count towards this submission.

• To show your competency in these software tools, these three assets should match or surpass the level of detail of assets created in the

Rubric for the Artistic Assets continues on the next page.

Part C: Game Prototype (25 marks)

With your prototype plan and assets, you must now develop a small functional and playable prototype that showcases one scene (that acts as a small area or level) with game mechanics that trigger events, and an end condition(s) - win, loss, and/or completion of level/area. The prototype must use your provided Scenario that has been randomly generated specifically for you.

Any time you wish to continue working on your Assignment, open it with Unity Hub. If it does not exist in the Unity Hub projects list, then you have not set it up correctly. If so, go back to “Setting up your Assignment for Part C” in Moodle and follow the instructions to fix this.

The template project has provided some things for you:

• A scene “MainScene” has been
  • ALWAYS use this scene when developing the main playable scene in your game

· In the Project Tab, folders have already been created for you. Use them to keep asset files organised.

• (Depending on Unity preferences, your project tab will look like one of the screenshots to the right) à

· If you do not use the template and/or organised folder structure, penalties will apply!

• Assets that YOU create are stored in the following folders:
  • Interface – Store all interface art assets created by yourself within GIMP (including Part B interface art).
  • Materials – Store all materials created by yourself within Unity, or from GIMP (including Part B textures).
  • Models – Store all 3D models created by yourself within Blender (including Part B models).
  • Prefabs – Store all prefabs created by yourself within
  • Scenes – This folder already contains a blank scene called “MainScene”. Your main prototype scene must be built in this Store additional scenes created by yourself in this folder (if any).
  • Scripts – Store all C# scripts created by yourself within Unity/Visual
  • – you can create additional folders to store assets created by yourself if they do not fit in to any of these Eg: “Animators”, “Audio”, “Particles”, etc.

· Assets that you download from the Unity Asset Store MUST be placed in:

• Unity Store Assets – To store any assets downloaded from the Unity Asset

o When sourcing additional assets, you must use the Unity Asset Store, choose free assets, and provide a link to that asset in your brief report. Do not download assets from any other source.

• You cannot download and use pre-built scene assets, kits or templates. Your scenes must be constructed by

• Packages – created by default for Do not remove, but you can ignore it during development.

Part C Requirements:

There are a number of requirements that you must adhere to when completing this assessment task:

Art Assets

• There are no requirements to develop any more 2D or 3D art assets yourself (this was completed in Part B), but you can if you want, just be aware that these newly created assets will not be marked separately and take additional development time that could be better spent on your scene and programming

o Any assets that you create yourself should be placed in the appropriate project folder in Unity.

• When sourcing additional assets, you must use the Unity Asset Store, and provide a link to the asset in your brief report. Do not download assets from any other source. Unity has a huge library of over 6000 free premade assets you can import and use, and not limited to just art assets (see Lab 6, Exercise 3 for instructions on importing free assets from the Unity Asset Store).
  • Unity Store assets sourced online MUST be placed in the “Unity Store Assets” project folder in Unity. This includes Unity’s own “Standard Assets” which is provided to you in Moodle Level
  • These assets should be used appropriately within your prototype to flesh out your scene

Scene(s) & Objects

• The main playable game scene must be built in the provided project template scene called “MainScene”.

· Remember that you are allowed to download objects from the Unity Asset Store to help populate your scene, BUT you CANNOT download and use a pre-built scene, kit or template. Your scene(s) must be constructed by yourself with your own placement of different objects.

• Unity can be used to develop a Terrain for your generated scenario environment (see Lab 6 for Unity 3D Terrain).
• Primitive objects can be placed in Unity, but may detract from the design, unless arranged into an elaborate scene. You are better off populating the scene with Unity Store Asset objects appropriate for your world/environment.
• Prefabs should be created for objects that require multiple instances in the game Place in “Prefabs” folder.
• Aim for engaging use of Objects (your own Part B created assets, plus additional free Unity Store assets) including 3D objects such as the player, props, cameras, light sources and other game objects to create your

Components

• Components should be added to your game objects where appropriate, such as:
  • Animators. Examples: Opening doors, moving platforms, premade Keep it simple.
  • Rigidbody for objects requiring physics behaviour / physical
  • Colliders for objects that can be collided with, and possibly require scripted collision
  • Colliders with triggers for objects to set up a scripted triggerable
  • Materials on objects to distinguish them apart from one
  • And other components such as Audio, Particle System, Camera, and UI components as
  • NOTE: Transform is a required component and is not considered for marking
  • NOTE: Mesh Renderer is a required component of a 3D model and is not considered for marking

Player Controller

• It is not expected for you to develop your own player controller. The labs have shown you how to use and modify the standard assets Player Controllers. You can use one of the standard asset controllers, download a different one from the Unity asset store, or create your own.
• Your player controller must function correctly and support your generated Scenario (especially the player viewpoint).

Scripts

• It is expected that you can develop your own C# scripts to create new events and behaviours in your prototype (see Labs 4 to 10, and Lecture Projects 8 and 10, regarding triggered events in Unity). Your randomly generated scenario requires the following events:
  • A dialogue event with a non-controllable
    • The type of dialogue is random for each student (see your generated Scenario in Moodle).
      • (Lecture 7 and 8 has multiple dialogue event examples. When the player approaches a character, some text appears on )
    • An assigned event that should display interface information onscreen to the player when
      • The type of event is random for each student (see your generated Scenario in Moodle).
        • (Labs 5 to 10 cater to all events that could be randomly assigned. For example, Lab 5 contains an event to collect coin objects, which updates the count score on the )
      • An Additional event of your own choice that should display interface information onscreen to the player when
        • This event could be anything you like, but it should suit your generated
      • You will also need to use Scripts to complete these remaining requirements:
        • End Condition(s) - win, loss, and/or completion of prototype
          • All prototypes require an ending condition that triggers winning (or completion) of the prototype (this is in addition to the other events above). This should be accompanied by a message to the player that they have won (or completed) the
          • In addition, you may (or may not) have a condition for losing, that should also output to the player that they have

o Comments

• Place your name and student ID at the top of scripts that you have
• You can learn from scripting guides on the internet, but any code you implement or adapt from ANY external source must be referenced using code commenting. This will show you have adequately researched and adapted them to your generated
  • Make sure all code adapted from external sources are clearly identified where they begin and end with comments, or it could be considered

· All scripts you create MUST be placed in your “Scripts” project folder in Unity.

Brief Report

You should also submit a written brief report detailing what you have done. A template is provided on Moodle to make this easier for both you and your marker. This report will address several items such as references to Unity Store Assets used, script/event details, known bugs and limitations, and how to play and win/lose your prototype.

Details are clearly presented in the template on what to include. Fill it in carefully. Be aware that:

• It is easy to determine if you claim someone else’s scenes, assets or scripts as your own, and this will be penalised, and may be considered for plagiarism.
• Be honest about limitations or known bugs in the game. It may help the marker to determine if you have attempted a task but could not get it working, in which some criteria still awards marks for the