Skip to content

Latest commit

 

History

History
31 lines (18 loc) · 2.18 KB

Game_Engine.md

File metadata and controls

31 lines (18 loc) · 2.18 KB

The SuperTux game engine is structured as follows:

  1. On startup, main.cpp instantiates a single MainLoop (mainloop.cpp) that is run until the application terminates.
  2. The MainLoop manages, updates and draws all Screens, Controllers, Menus and the Console.

:*A Screen (screen.hpp) is the abstract base class for code that the MainLoop runs exclusively and full-screen.

Probably the most important Screen is the GameSession (game_session.cpp), which actually runs a Level (level.cpp).

Examples of other Screens are:

  1. The SuperTux title screen (title.cpp)
  2. a world map (world.cpp)
  3. an intro text scroller (textscroller.cpp)

A GameSession loads and runs a single Level, which consists of multiple, separate parts, the Sectors. Sectors contain the various GameObjects that can be encountered in SuperTux.

Examples of such GameObjects are the Badguys, Players and TileMaps, but also Thunderstorm controllers, the currently visible viewport (i.e. a Camera object), the sector's time limit, etc.

More in-depth information about the game engine can be found in the source code itself, e.g. as Doxygen HTML Documentation, or on pages in :Category:Game Engine, most notably:

Category:Game Engine