Engine:CVAR module - Revision history

Bear: Undo revision 21624 by Bear (talk)

2023-10-17T05:12:39Z

Undo revision 21624 by Bear (talk)

← Older revision		Revision as of 05:12, 17 October 2023
Line 1:		Line 1:
	{{dev/uicvar}}		{{dev/uicvar}}
	Base name for 'world' module, without platform postfix or extensions.		Base name for the default 'world' module, without platform postfix or extensions.
	<kua>set module 'game'</kua>		<kua>set module 'game'</kua>

Bear at 05:11, 17 October 2023

2023-10-17T05:11:56Z

← Older revision		Revision as of 05:11, 17 October 2023
Line 1:		Line 1:
	{{dev/uicvar}}		{{dev/uicvar}}
	Base name for ~~the default~~ 'world' module, without platform postfix or extensions.		Base name for 'world' module, without platform postfix or extensions.
	<kua>set module 'game'</kua>		<kua>set module 'game'</kua>

Bear at 05:01, 17 October 2023

2023-10-17T05:01:25Z

← Older revision		Revision as of 05:01, 17 October 2023
Line 1:		Line 1:
	{{dev/uicvar}}		{{dev/uicvar}}
	Base name for 'world' module, without platform postfix or extensions.		Base name for the default 'world' module, without platform postfix or extensions.
	<kua>set module 'game'</kua>		<kua>set module 'game'</kua>

Bear: /* Details */

2023-10-17T00:58:50Z

Details

← Older revision		Revision as of 00:58, 17 October 2023
Line 21:		Line 21:
	World is loaded separately through configuration, and lives on its own managed by the engine 'World' module. A library may create and manage sets of entities and control how they interact and provide other services.		World is loaded separately through configuration, and lives on its own managed by the engine '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. Or no library may load~~, if the world config and data implicitly everything they need, messaged from elsewhere like remotely, and/or is provided scripts or addons~~.		During world load, the world may manage which native libraries if any get loaded. A library may also cause a different world to load. Also, no library may load at all.

	; Library load name and path:		; Library load name and path:

Bear: /* Details */

2023-10-17T00:54:49Z

Details

← Older revision		Revision as of 00:54, 17 October 2023
Line 19:		Line 19:
	; Lifetime		; Lifetime

	~~In the engine the world itself~~ is loaded separately through configuration ~~and other data~~, and lives on its own managed by the engine 'World' module. A library may create and manage sets of entities and control how they interact and provide other services.		World is loaded separately through configuration, and lives on its own managed by the engine '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. Or no library may load, if the world config and data implicitly everything they need, messaged from elsewhere like remotely, and/or is provided scripts or addons.		A world load may manage which native libraries if any, get loaded. And a native world library may cause a different world to load. Or no library may load, if the world config and data implicitly everything they need, messaged from elsewhere like remotely, and/or is provided scripts or addons.

Bear: /* Details */

2023-10-17T00:02:00Z

Details

← Older revision		Revision as of 00:02, 17 October 2023
Line 19:		Line 19:
	; Lifetime		; Lifetime

	In the engine the world itself is ~~established~~ separately through configuration and other data ~~loads. It exists~~ and lives on its own managed by the 'World' module. A library may create and manage sets of entities and control how they interact and provide other services.		In the engine the world itself is loaded separately through configuration and other data, and lives on its own managed by the engine '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, and/or scripts or addons.		A world load may manage which native libraries if any, get loaded. And a native world library may cause a different world to load. Or no library may load, if the world config and data implicitly everything they need, messaged from elsewhere like remotely, and/or is provided scripts or addons.

	; Library load name and path:		; Library load name and path:

Bear: /* Details */

2023-10-16T23:57:55Z

Details

← Older revision		Revision as of 23:57, 16 October 2023
Line 19:		Line 19:
	; Lifetime		; 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.		In the engine the world itself is established separately through configuration and other data loads. It exists and lives on its own 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 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, and/or scripts or addons.

	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:

Bear: /* Details */

2023-10-16T23:56:28Z

Details

← Older revision		Revision as of 23:56, 16 October 2023
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:

Bear: /* Details */

2023-10-16T23:34:14Z

Details

← Older revision		Revision as of 23:34, 16 October 2023
Line 15:		Line 15:
	'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.

	~~The~~ 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.

	; Library load name and path:		; Library load name and path:

	The actual load path ~~for the world library~~ set with [[CVAR lib_path]], and final library file name will be calculated from the 'module' name and the platform suffixes. See [[CVAR lib_path]] for the list of suffixes and explanation.		The actual load path set with [[CVAR lib_path]], and final library file name will be calculated from the 'module' name and the platform suffixes. See [[CVAR lib_path]] for the list of suffixes and explanation.

	The ~~world~~ library state typically unloads when the world unloads or changes, and loads again when the world loads again. The actual OS module that is the library may or may not, from the OS standpoint, ever be unloaded from the engine process, once loaded.		The library state typically unloads when the world unloads or changes, and loads again when the world loads again. The actual OS module that is the library may or may not, from the OS standpoint, ever be unloaded from the engine process, once loaded.

	== Examples ==		== Examples ==

Bear: /* Details */

2023-10-16T23:31:14Z

Details

← Older revision		Revision as of 23:31, 16 October 2023
Line 21:		Line 21:
	The actual load path for the world library set with [[CVAR lib_path]], and final library file name will be calculated from the 'module' name and the platform suffixes. See [[CVAR lib_path]] for the list of suffixes and explanation.		The actual load path for the world library set with [[CVAR lib_path]], and final library file name will be calculated from the 'module' name and the platform suffixes. See [[CVAR lib_path]] for the list of suffixes and explanation.

	The world library state typically unloads when the world unloads or changes, and loads again when the world loads again. The actual OS module that is the library may or may not, from the OS standpoint, ever be unloaded process, once loaded.		The world library state typically unloads when the world unloads or changes, and loads again when the world loads again. The actual OS module that is the library may or may not, from the OS standpoint, ever be unloaded from the engine process, once loaded.

	== Examples ==		== Examples ==