Quote: "a timer stop would be nice "
Technically it never starts. When you say "timerstart" all it really does is syncronize the "hudtimer" with the system timer. When you check "timergreater" it checks the distance that has accumulated between the "hudtimer" and the system timer. Since the system timer never stops, the hudtimer cannot stop. This is also why if you check "timergreater" without ever having said "timerstart", it will return TRUE since the distance between hudtimer (initially 0) and the system timer is most likely MASSIVE (Think hours worth of milliseconds).
The only way you can do this is to setup a "stoptimer" flag, and then during EVERY frame, have the hudtimer increment by how much the system timer had incremented during that frame. That way, if you "stop" the script timer, it will
appear to have stopped because it will maintain the distance it had accumulated between itself and the system timer.
In all honesty, I can't think of a script where a stoptimer command would be of any help. The only scenarios I can think of would still be acheivable without it.
The one and only,
