Tf logic cp timer: Difference between revisions
		
		
		
		
		
		Jump to navigation
		Jump to search
		
				
		 

 
 Bug:When The assigned control point is captured, the logic tied to
Bug:When The assigned control point is captured, the logic tied to 
		
	
|  (Added a warning about a bug regarding the OnCountdownStart output.) |  (-added class hierarchy, cleanup) | ||
| Line 1: | Line 1: | ||
| {{Underlinked|date=January 2024}} | {{Underlinked|date=January 2024}} | ||
| {{ | {{LanguageBar}} | ||
| {{ | {{CD|CCPTimerLogic|file1=tf_gamerules.cpp}} | ||
| {{This is a|point entity|name=tf_logic_cp_timer|game=Team Fortress 2}} It runs a timeout timer for a [[team_control_point|control point]] and adds itself to the HUD for that point. This entity is used for DeGroot Keep's final point. | |||
| {{bug|When The assigned control point is captured, the logic tied to <code>OnCountdownStart</code> will be ran extremely quickly, roughly every 20 ticks. Make sure all logic tied to this entities outputs are controlled by [[logic_relay|logic_relays]], as the logic inside ''those'' will not be triggered.}} | {{bug|When The assigned control point is captured, the logic tied to <code>OnCountdownStart</code> will be ran extremely quickly, roughly every 20 ticks. Make sure all logic tied to this entities outputs are controlled by [[logic_relay|logic_relays]], as the logic inside ''those'' will not be triggered.}} | ||
| ==Keyvalues== | == Keyvalues == | ||
| {{KV  | {{KV Targetname}} | ||
| {{KV TeamNum|tf2=1}} | {{KV TeamNum|tf2=1}} | ||
| {{KV|Control Point|target_source|The control point the timer applies to}} | {{KV|Control Point|target_source|The control point the timer applies to}} | ||
| {{KV|Timer length (in seconds)|int|How long the timer should be, in seconds.}} | {{KV|Timer length (in seconds)|int|How long the timer should be, in seconds.}} | ||
| == Outputs == | |||
| {{O|OnCountdownStart|The countdown has begun, since the control point is now available for capture.}} | |||
| {{O|OnCountdownEnd|The time has counted down and the capture point is no longer eligible for overtime.}} | |||
| ==Outputs== | |||
| {{O  | |||
| {{ | |||
Revision as of 15:00, 25 September 2024

This article needs more  links to other articles to help
 links to other articles to help  integrate it into the encyclopedia. Please help improve this article by adding links
 integrate it into the encyclopedia. Please help improve this article by adding links  that are relevant to the context within the existing text.
 that are relevant to the context within the existing text.
January 2024
 links to other articles to help
 links to other articles to help  integrate it into the encyclopedia. Please help improve this article by adding links
 integrate it into the encyclopedia. Please help improve this article by adding links  that are relevant to the context within the existing text.
 that are relevant to the context within the existing text.January 2024

 
|  Class hierarchy | 
|---|
| CCPTimerLogic | 
|  tf_gamerules.cpp | 
tf_logic_cp_timer  is a   point entity  available in  Team Fortress 2. It runs a timeout timer for a control point and adds itself to the HUD for that point. This entity is used for DeGroot Keep's final point.
 Team Fortress 2. It runs a timeout timer for a control point and adds itself to the HUD for that point. This entity is used for DeGroot Keep's final point.
 Bug:When The assigned control point is captured, the logic tied to
Bug:When The assigned control point is captured, the logic tied to OnCountdownStart will be ran extremely quickly, roughly every 20 ticks. Make sure all logic tied to this entities outputs are controlled by logic_relays, as the logic inside those will not be triggered.  [todo tested in ?]Keyvalues
- Name (targetname) <string>[ Edit ]
- The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g. parentnameortarget).
 Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
TeamNum:
- Timer length (in seconds) ([todo internal name (i)]) <integer>
- How long the timer should be, in seconds.
Outputs
- OnCountdownStart
- The countdown has begun, since the control point is now available for capture.
- OnCountdownEnd
- The time has counted down and the capture point is no longer eligible for overtime.























