Skip to content
Martin Kelm edited this page Jul 31, 2013 · 23 revisions

This article contains an overview about the general game logic. But there is no warranty that this article is up to date and complete. You should use it as an introduction into the game logic only, and look into the source code / documentation after that. The game logic is in an early stage ...

Current demonstration video of running game logic

Launcher scripts

The game starts with a launcher script from the root folder. The file depends on the system you use.

For developers: The Google closures compiler has it own compiler launcher scripts, called compile.sh and compile-run.sh but you have to modify the absolute library path in the run script, to make it workable. Or you have to open lib/display/mct.html manually, which uses the compiled game logic file ...

Game start

... otherwise the game starts with lib/display/default.html which will load additional javascript logic files.

Loading library files

The game library contains three types of library files:

The lib/display/mct.js is an exception, because it is a compilation of all MCT logic files for the compiled version.

Initialization

The game has too initialization files calles init.js for game and display related contents.

Display contents

Display contents are:

Game contents are:

The audio manager is located in the game contents too, currently. But maybe it will combined in an seperate audio folder with the sub folders for music and effects from the sound folder.