Interface GameRunnerConfig

depends on canvas Type

"create" => a new canvas is created and attached to the canvas selector object "selector" => it is expected that the canvas selector points to a canvas

Only valid if mainloopType is MainLoopType.Fixed.

[OPTIONAL] Define any flags that helps to run your game.

Suggestions: "ios", "nativ", "desktop", or "demo" :-)

It's possible to have different mainloop behavior and controlls how update() is called.

when > 0 it will cap the FPS to the given value if the window has lost the fosus. This is useful during development when your laptop starts to scream at you while working on a game.

when > 0 it will cap the FPS to the given value.

Means the mainloop won't start automatically. This has to be done by hand.

Means built-in property-parser won't be set automatically. You can add them by yourself

Note

advanced

Means built-in resourceloader won't be set automatically.

Note

advanced

A global path-prefix used for all resources loaded using the ResourceManager.

This is useful when deploying the game into a environment where the paths of the executed javascript code does not match the dev-environment.

Name or list of names the start world.

For a very simple case one can simply set a string.

However, for certain patterns it's useful to start more than one world and in a controlled order.

Example 1: start two worlds at the same time

startWorlds: ["world1", "world2"]

Example 2: start 3 worlds in a controlled order

startWorlds: [["world1"], ["world2", "world3"]]

when world1 is active, world2 and world3 get activated.