Torque3D/Templates/BaseGame/game/data/TTR/TTR.cs

function TTR::onCreate(%this)
{
}

function TTR::onDestroy(%this)
{
}

function TTR::initServer(%this){}

function TTR::onCreateGameServer(%this){}

function TTR::onDestroyGameServer(%this){}

function TTR::initClient(%this){}

function TTR::onCreateClientConnection(%this){}

function TTR::onDestroyClientConnection(%this){}
Reorg of the probe initialization/update code to streamline parts of it, and make it flow more obviously Added some initial asset stuffs for Das Boot for building out a better testing level. 2019-06-04 00:21:52 -05:00			`function TTR::onCreate(%this)`
			`{`
			`}`

			`function TTR::onDestroy(%this)`
			`{`
			`}`

Caught the main modules up to new module script file paradigm Have initServer only get called when a server is actually started for the first time Added utility method callGamemodeFunction to streamline exec'ing of gamemode function calls Added onClientConnect gamemode function, called when the client establishes the connection Added onInitialControlSet gamemode function, called when the client actively gains control in the game, to allow gamemodes to special override GUI settings or input commands Cleaned up init'ng of the engine so stock UI module isn't required to trip configuration of the canvas Added fallback so if nothing set the main content control for the UI after boot, we attempt to set the defined mainMenuGUI, on the chance nothing explicitly sets it on load 2019-09-02 16:13:24 -05:00			`function TTR::initServer(%this){}`

			`function TTR::onCreateGameServer(%this){}`

			`function TTR::onDestroyGameServer(%this){}`

			`function TTR::initClient(%this){}`

			`function TTR::onCreateClientConnection(%this){}`

			`function TTR::onDestroyClientConnection(%this){}`