JeffR c5ae9af0ae Core now spawns a ControlObject directly, with callbacks allowing overriding of values to control what spawns (and what occurs afterwards) to tie several tracking variables to a given client connection. ... By default this list of variables would be: %this.spawnClass = "Camera"; %this.spawnDBType = "CameraData"; %this.spawnDataBlock = "Observer"; %this.playerSpawnGroups = "PlayerSpawnPoints PlayerDropPoints"; %this.spawnPoint = ""; %this.spawnLocation = "0 0 0"; Also adds several callbacks so that these values can be overridden by modules and gamemodes, kicked off from the %client.spawnControlObject(); command : callOnModules("setSpawnObjectType", "Game", %this); callGamemodeFunction("setSpawnObjectType", %this); callOnModules("setSpawnPoint", "Game", %this); callGamemodeFunction("setSpawnPoint", %this); callOnModules("onPostSpawn", "Game", %this); callGamemodeFunction("onPostSpawn", %this); This is to ensure that a game mode can supersede modules, but even modules can dictate spawn behaviors for minimalist implementations and drop-in interop support		2024-12-21 02:11:35 -06:00
..
client	Removes old remaining refs to PauseMenu	2024-06-28 20:47:42 -05:00
shared	Core now spawns a ControlObject directly, with callbacks allowing overriding of values to control what spawns (and what occurs afterwards) to tie several tracking variables to a given client connection.	2024-12-21 02:11:35 -06:00