CompileTrigger: Difference between revisions
		
		
		
		
		
		Jump to navigation
		Jump to search
		
				
		
 Note:Different textures will have no functional effect, unless paired with other Shader Parameters.
Note:Different textures will have no functional effect, unless paired with other Shader Parameters.
		
	
| SirYodaJedi (talk | contribs) mNo edit summary | SirYodaJedi (talk | contribs)  m (SirYodaJedi moved page %CompileTrigger to CompileTrigger: move to prevent external links from being eaten) | 
| (No difference) | |
Revision as of 17:30, 24 March 2025
Compiles the texture to be used for a Trigger. Effectively identical to %CompileNoLight, except when VBSP is compiled with -nodrawtriggers.
Generally "Tools/toolstrigger" could be used for any trigger, but if a mod/map has multiple types of brush entities that use Tools/toolstrigger, one could make multiple tool textures to differentiate the types of entities easier, such as trigger_hurt, trigger_once, trigger_multiple, parallax_obb, etc.
 Note:Different textures will have no functional effect, unless paired with other Shader Parameters.
Note:Different textures will have no functional effect, unless paired with other Shader Parameters.Example
Example uses  
LightmappedGeneric, however  
UnlitGeneric also works as well; %CompileTrigger implies %CompileNoLight.
LightmappedGeneric
 {
 	$translucent 1
 	$basetexture "Tools/toolstrigger"
 	"srgb?$basetexture" "Tools/toolstrigger-dx10"
 	"%compiletrigger" 1
 	"%keywords" "airexchange,borealis,c17downtown,c17industrial,c17sewers,c17skyscraper,c17trainstation,combine,kraken,wasteland"
 }