Time Travel: Difference between revisions
m (better mentioned on blast page) |
No edit summary |
||
| Line 7: | Line 7: | ||
<youtube>JsuMQSggHEA</youtube> | <youtube>JsuMQSggHEA</youtube> | ||
== | == Developer information == | ||
Through m_flMaxspeed, the player's speed is increased to 520 HU/s (the maximum speed on ground). The player is also given condition 66 (TFCond_StealthedUserBuffFade). The player is blocked from attacking using the netprops m_flNextPrimaryAttack and m_flNextSecondaryAttack and by blocking the IN_ATTACK button. The former is preferred due to the latter having the blocked action delayed by ping amounts, but only having the former makes the sapper usable during time travel, which is why two different attack-blocking methods are employed. | Through m_flMaxspeed, the player's speed is increased to 520 HU/s (the maximum speed on ground). The player is also given condition 66 (TFCond_StealthedUserBuffFade). The player is blocked from attacking using the netprops m_flNextPrimaryAttack and m_flNextSecondaryAttack and by blocking the IN_ATTACK button. The former is preferred due to the latter having the blocked action delayed by ping amounts, but only having the former makes the sapper usable during time travel, which is why two different attack-blocking methods are employed. | ||
[[Category:Powerups]] | [[Category:Powerups]] | ||
Revision as of 20:18, 4 March 2020
Time Travel is the sixth powerup in Fortress Blast. It was included in Fortress Blast's initial release and is inspired by the game 
Marble Blast Gold.
It turns the user invisible, super fast, and in third person for 3 seconds, but during this time they cannot attack. This can be used to get past difficult obstacles or as an escape method.
Developer information
Through m_flMaxspeed, the player's speed is increased to 520 HU/s (the maximum speed on ground). The player is also given condition 66 (TFCond_StealthedUserBuffFade). The player is blocked from attacking using the netprops m_flNextPrimaryAttack and m_flNextSecondaryAttack and by blocking the IN_ATTACK button. The former is preferred due to the latter having the blocked action delayed by ping amounts, but only having the former makes the sapper usable during time travel, which is why two different attack-blocking methods are employed.
