Talk:Trigger playermovement: Difference between revisions
Jump to navigation
Jump to search
Innocentive (talk | contribs) (Out-of-date information?) |
(→Trigger playermovement not reseting after round end: new section) |
||
| Line 1: | Line 1: | ||
This page appears to be completely out of date. The information concerning the spawnflags is not accurate. Especially the auto-walking doesn't seem to be featured anymore. --[[User:Innocentive|Innocentive]] 12:07, 27 January 2013 (PST) | This page appears to be completely out of date. The information concerning the spawnflags is not accurate. Especially the auto-walking doesn't seem to be featured anymore. --[[User:Innocentive|Innocentive]] 12:07, 27 January 2013 (PST) | ||
== Trigger playermovement not reseting after round end == | |||
So my problem is, if playermovement is active with duck enabled at round end, at the next round the player is not ducking anymore, but his speed still remains as low as in duck-state. If I re-enter the trigger in the next round, the player gains his full velocity again. How to make sure, that trigger_playermovement is disabled at round end? (It's in an instance) | |||
Revision as of 14:34, 29 September 2014
This page appears to be completely out of date. The information concerning the spawnflags is not accurate. Especially the auto-walking doesn't seem to be featured anymore. --Innocentive 12:07, 27 January 2013 (PST)
Trigger playermovement not reseting after round end
So my problem is, if playermovement is active with duck enabled at round end, at the next round the player is not ducking anymore, but his speed still remains as low as in duck-state. If I re-enter the trigger in the next round, the player gains his full velocity again. How to make sure, that trigger_playermovement is disabled at round end? (It's in an instance)