Torque3D/Templates/Modules/FPSGameplay/FPSGameplay.module

<ModuleDefinition
	ModuleId="FPSGameplay"
	VersionId="1"
	Description="Starter module for FPS gameplay."
	ScriptFile="FPSGameplay.cs"
	CreateFunction="create"
	DestroyFunction="destroy"
	Group="Game"
    Dependencies="clientServer=1,UI=1">
	<DeclaredAssets
        canSave="true"
        canSaveDynamicFields="true"
        Extension="asset.taml"
        Recurse="true" />
</ModuleDefinition>
Initial implementation of the new Base Game Template and some starting modules. This makes some tweaks to the engine to support this, specifically, it tweaks the hardcoded shaderpaths to defer to a pref variable, so none of the shader paths are hardcoded. Also tweaks how post effects read in texture files, removing a bizzare filepath interpretation choice, where if the file path didn't start with "/" it forcefully appended the script's file path. This made it impossible to have images not in the same dir as the script file defining the post effect. This was changed and the existing template's post effects tweaked for now to just add "./" to those few paths impacted, as well as the perf vars to support the non-hardcoded shader paths in the engine. 2017-02-24 02:40:56 -06:00			`<ModuleDefinition`
			`ModuleId="FPSGameplay"`
			`VersionId="1"`
			`Description="Starter module for FPS gameplay."`
			`ScriptFile="FPSGameplay.cs"`
			`CreateFunction="create"`
			`DestroyFunction="destroy"`
			`Group="Game"`
			`Dependencies="clientServer=1,UI=1">`
Corrects level asset defines in the FPSGameplay and SpectatorGameplay modules. 2018-02-01 01:50:38 -06:00			`<DeclaredAssets`
			`canSave="true"`
			`canSaveDynamicFields="true"`
			`Extension="asset.taml"`
			`Recurse="true" />`
Initial implementation of the new Base Game Template and some starting modules. This makes some tweaks to the engine to support this, specifically, it tweaks the hardcoded shaderpaths to defer to a pref variable, so none of the shader paths are hardcoded. Also tweaks how post effects read in texture files, removing a bizzare filepath interpretation choice, where if the file path didn't start with "/" it forcefully appended the script's file path. This made it impossible to have images not in the same dir as the script file defining the post effect. This was changed and the existing template's post effects tweaked for now to just add "./" to those few paths impacted, as well as the perf vars to support the non-hardcoded shader paths in the engine. 2017-02-24 02:40:56 -06:00			`</ModuleDefinition>`