time: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
mNo edit summary
m (VBS2 scripting category removal)
Line 52: Line 52:
[[Category:Command_Group:_Mission_Information|TIME]]
[[Category:Command_Group:_Mission_Information|TIME]]
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]]
[[Category:Scripting Commands VBS2|{{uc:{{PAGENAME}}}}]]

Revision as of 05:20, 19 July 2011

Hover & click on the images for description

Description

Description:
Time elapsed since mission started (in seconds).
Groups:
Uncategorised

Syntax

Syntax:
Number = time
Return Value:
Number

Examples

Examples:
Example needed

Additional Information

See also:
daytimedatedateToNumber

Notes

Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note

Notes

Posted on August 4, 2006 - 12:02
hardrock
Notes from before the conversion: Not to be confused with _time. Within a script, the reserved local variable _time returns the time elapsed since the script started running. Note that the value of time is not saved when the mission is saved and so will be reset to zero when a mission is restarted from a saved position. The value of _time is saved correctly and will resume from where it was.
Posted on January 5, 2007 - 12:24
Giova
Notes from before the conversion: time works properly in sqf called with execVM command. In an other hand, _time does not works in sqf called with execVM command.(Arma v1.02.5103GER)
Posted on October 02, 2010 - 12:02
teaCup
On overloaded servers (below ~10 server FPS), time readings are unreliable. Seconds actually take longer. While the clients keep a steady tempo, server time lags behind, resulting in considerable offset between client and server time (easily 30 minutes for a 2 hour game). Client time is synchronised to server time during JIP, but other than that it runs independently.

Bottom Section