49
edits
→Details
| Line 13: | Line 13: | ||
Name of the world native library to load. | Name of the world native library to load. | ||
'World' in this context means a graphically or otherwise conceptually interactive environment, and is apart from any regular 2D UI environment, or may have no direct user interfaces. | 'World' in this context means a graphically or otherwise conceptually interactive environment, and is apart from any regular 2D UI environment, or may have no direct user interfaces. | ||
A world library typically loads when the 'world' loads and provides support for managing discrete world components how they interact and can act as a sink and/or source for messaging with other systems. | A world library typically loads when the 'world' loads and provides support for managing discrete world components how they interact and can act as a sink and/or source for messaging with other systems. | ||
; Lifetime | |||
The world itself is established separately through configuration and other data loads. And it exists on its own in the engine managed by the 'World' module. A library may create and manage sets of entities and control how they interact and provide other services. | |||
A world load may manage which native libraries if any, get loaded. And a native world library may cause a different world to load. | |||
A native world library also may never load. The world config and data implicitly everything they need, messaged from elsewhere like remotely, or via solely through scripts or addons. | |||
; Library load name and path: | ; Library load name and path: | ||