GDP102 Game Design Principles Assessment 3

Context:

Drawing from all the design theory covered in GDP102, you will create a digital game vertical slice and reflect on the process of game design and creation. This assignment is designed to encourage you to engage with the principles of level design, context & narrative design, unique mechanics, USPs, and more. Working in teams or individually, this summative aims to push your creativity and interpersonal communication.

You will be designing and creating a digital game segment/slice with a focus on creating an interesting space for gameplay. As this is a gameplay segment/slice, your game is not expected to be a full-length production. Instead, you are aiming for a well-designed segment that represents what the game, in its full-length, could be like. Your goal is to explore and demonstrate game design principles through existing and established game engine tools and assets by creating an engaging and interesting gameplay space for your player to interact with.

You will first need to design your (original) game context (both theme & mechanics), this can be based on your Assessment 2 pitch, and then utilise fundamental game design tools and a game development engine (such as Unity or Unreal) to create your game segment.

Practically, this means you will be creating an interactive game level or small arcade game that utilises simple scripting or blueprints, has an appropriate scope, aesthetic presentation and demonstrates your ability to apply game design theory to a unique game design concept.

Instructions:

1.    Create a functional/playable arcade game or game level in an industry-standard 3D game engine (Unity or Unreal).

Your game segment must either be a single game level/map or a small arcade game consisting of several (3-5) small arcade puzzles depending on complexity.

2.    Create a short presentation (3-4min) which introduces the game context and highlights the design principle used.

•    Your presentation should also contain documentation of an iterative process.

i.   Simple dot points with images and diagrams.

ii.    Evidence of an iterative workflow, such as references, mood board, sketches and screenshots of draft designs.

iii.    Reflection on the design challenges you faced and highlight the ones you overcame (with evidence).

Minimum Game Requirments -

•    Functional player control and interaction.

•    1 functional level (or approx. 5min gameplay)

o Contains a clear objective.

o Contains a simple form of interactivity.

This is your fundamental mechanics (i.e running, jumping, shooting).

This does not need to be more complex than what a game template provides.

o Explores the form of interactivity through game/level design.

o Contains a measure for success.

No open worlds, you must be able to ‘complete’ the level/game.

Must be in the form of an achievable challenge.

•    I.e Defeat the enemy waves, solve the puzzle, find the key to the door.

•    Clear thematic/aesthetic direction.

o The visual and contextual theme must be evident but not necessarily polished.

I.e A detailed grey box (Blockout) with a first lighting pass and contextual placeholder assets where necessary.

o Sound and music which provides any necessary thematic context or player feedback.

Submission Instructions:

•    Game Project

o Game engine project folder (zipped)

o Game executable (.exe build, zipped)

Must be playable on Windows 10.

•    Game Presentation (3-4min)

o Campus classes (In-class during Week 12, before Week 12 submission)

This will be treated as a work-in-progress presentation

o Online pre-recorded in PowerPoint (Submitted at Week 12 submission).

o Both - a screen recorded playthrough of the game/level.