Engine Core

Singleton engine lifecycle, application base class, and main loop. More...

Files
file	Application.h
	Abstract base class for the user-defined game or lab application.
file	Engine.h
	Central singleton that owns and coordinates all engine subsystems.

Detailed Description

Singleton engine lifecycle, application base class, and main loop.

Engine lifecycle, application contract, and shared types.

The two classes that form the entry point of every Monad Engine program:

• Engine — singleton that owns all subsystems and drives the main loop.
• Application — user-subclassed interface (Init / Update / Destroy).

Typical startup:

Engine &e = Engine::GetInstance();
e.SetApplication(new MyGame());
e.Init(1280, 720);
e.Run();
e.Destroy();

The Core module hosts the entry points every game touches:

• mnd::Engine — singleton that owns every subsystem and drives the main loop.
• mnd::Application — abstract base your game subclasses to receive Init / Update / Destroy callbacks.

Every subsystem in the engine is reachable from Engine::GetInstance(), so once a frame has begun all of them can be queried without passing references through layers.

See also

Subsystem Map