Architecture of Chickenshock

Purpose

Chickenshock is a minigame that is part of the Gamify-IT platform. The intention with this game is to make answering single choice questions fun.

Table of Contents

• Links

• Purpose

• General code structure

• Starting the service

• What to look at

• What to ignore

• Known Design Flaws

• Known Bugs

• Tests

Links

• The user docs explain how to play the game.

• The program code is available here.

• The overview of the architecture can be found here.

• The backend architecture is described here.

Purpose

Being a fun-to-play minigame that lets users choose one correct answer from a bunch of wrong answers

General code structure

Unity uses C# scripts.
There is no “main”-class in Unity scripts.
Each script that is put on a GameObject can have a Start method (called once when the GameObject is created), an Awake method (called once before Start), and an Update method (called on each frame).
If the GameObject is destroyed everything attached to it will be destroyed as well, meaning no script attached to the destroyed GameObject will be executed again.

We decided to split our Chickenshock game into 3 main scenes:

• Main Screen: contains the content of the start screen

• Game: contains the content of the main game

• End Screen: contains the content of the end screen

Starting the service

See the README.

What to look at

Generally all .cs files. The key script files that contain most of the actual game behavior are the Global.cs file and the ShootWeapon.cs file.

What to ignore

We created a ChickenshockProperties file for less redundance. This is a static class because there is no option we know of that uses a normal .properties file in Unity.

Known Design Flaws

N/A

Known Bugs

An up-to-date list of open bugs can be found at https://github.com/orgs/Gamify-IT/projects/6/views/11 by searching for Chickenshock.

Tests

In general, the following things are tested for Chickenshock:

• everything manually with a testplan