COMP1331 Intro to Games Design & Development

Game Engine Plug-in: Team-based NPC Behaviour Simulation

This project is specifically for students who have already developed a Game Engine through their work on the 2nd year Games module and are continuing that work on the 3rd year Games module.  Your Game Engine Architecture will need to be developed to the extent that a Behaviour Manager element already exists.

In this project, you will design, build, and test an extension to the Behaviour Manager of your Entity-based Game Engine Architecture, to allow NPCs to be implemented with team behaviours (eg shoaling or 'squadding').  This will require a hierarchical approach to the AI Components of your Engine.  Testing will require verification of your Engine + demo software against a model of a chosen team-based behaviour.


Serious Games: Scenario Planning Climate Disaster

Theoretical / Design-Build-Test. This outline is for a number of possible projects that could be pursued around the use of Serious Games to model and plan for climate disaster.

An interesting resource is the climate countdown graphic provided by MCC Berlin at - scroll down about halfway.  The graphic provides an estimate of the duration until 1.5C and 2.0C warming is reached.  The estimate is based on real-time data, and this could provide a context to build your project around.  There is potential, for example, to attempt to build-in a climate tipping-point that translates as a 'climate disaster'

This description is a work-in-progress, please contact Marc Price for further details if you are interested.


Entity-Component-System (ECS) Game Engine Architecture

If you completed your 2nd year games module with a more-or-less complete game engine architecture, you might enjoy the challenge of creating a component-based (ECS) game engine for your 3rd year project.

This would be a DBT project that is primarily focused on Software Engineering and Game Development. You can use any programming language of your choice, however, you might find it less challenging to use a language that you are already familiar with. Although some kind of demo will be required to test and showcase the software, producing a playable game prototype would be beyond the scope of the project.

Key challenge: how to design, implement, and verify an engine with the component-based paradigm.

Considerable background research on the component-based approach would be necessary prior to starting this project.

As this is a DBT, the question is what would be an appropriate test?  To a certain extent, this is something that you would have to answer yourself, via secondary research.  However, the most often cited reason for opting for ECS architecture over an OO entity-based architecture, is performance.  This isn't the only lens you can take, but if you choose this, then your test could be a comparison between a newly created ECS engine and an OO entity-based engine.  Your secondary research would then need to also look at benchmarking tests to see how comparisons have been done by others, and which would be most suited in this context.

Another comparison test might be to look at software analysis of ECS  vs OO (eg in terms of Cohesion and/or Coupling).  In this case, your secondary research would need to also look at how others have measured these things.

Although the artefact (ie your software) will be a key deliverable, we will also need to see: