TbeSystemManager

tbeSystemManager

The TbeSystemManager Component has to be added to your scene. The TBE Setup tool helps you with this.

It also must be the first user component that gets loaded (Check Script loading order in Unity). If you are using the Quickstart, then this is already the case.

Outgoing references

The system Manager references:

Tbe Database Location

If there is exactly one TbeDatabaseLocation in the project, the system manager will automatically select it.

TbeSceneSettings

  • The scope of TbeSceneSettings is dictated by the TbeSystemManager. You can have multiple TbeSceneSettings, but of course only one per scene.

  • Inside TbeSceneSettings there is another reference and that is the UI Skin Settings.

TBE comes with sensible defaults for all of these settings.

So the outgoing references look like this:

diagram

Other Required Components

Other Components that are required at Runtime but are decoupled from the System Manager are:

  • ScenePlayerContext

    • Here you can give an Inventory definition for the player.

  • Needing no User attention:

    • ActorContainer

    • UnitManager

    • InputManager

Plugins

The system manager can have plugins and one plugin that is already included in TBE is the FramerateLimiter. When you take a look at it’s code you will see that all you have to do to create your own plugin is to extend SystemManagerPlugin.

FramerateLimiter

The limiting of the framerate is most useful for the built version of your game. If you don’t limit the framerate, the unity runtime will produce as many frames as it can and your computer will use more power and get hotter than required.