serverTime: Difference between revisions

From Bohemia Interactive Community
Jump to navigation Jump to search
m (Text replacement - "\|seealso= *\[\[([^ ]+)\]\], \[\[([^ ]+)\]\]" to "|seealso= $1 $2")
m (Text replacement - "\|seealso= *\[\[([^ ]+)\]\], \[\[([^ ]+)\]\]" to "|seealso= $1 ")
Line 31: Line 31:
|x1= <code>[[hint]] [[format]] ["Synced server time : %1", [[serverTime]]];</code>
|x1= <code>[[hint]] [[format]] ["Synced server time : %1", [[serverTime]]];</code>


|seealso= [[time]] [[diag_tickTime]] [[date]] [[missionStart]], [[estimatedTimeLeft]], [[estimatedEndServerTime]], [[systemTime]], [[systemTimeUTC]]
|seealso= [[time]] [[diag_tickTime]] [[date]] [[missionStart]] [[estimatedTimeLeft]], [[estimatedEndServerTime]], [[systemTime]], [[systemTimeUTC]]
}}
}}

Revision as of 17:55, 20 January 2022

Hover & click on the images for description

Description

Description:
Returns the time since last server restart, synced to all clients in MP. The syncing is happening every 5 minutes, but you can force the next sync earlier by executing estimatedTimeLeft command. The time returned is also different to the time returned by time and diag_tickTime commands on server. Returns 0 in SP.

Known issues before Arma 3 v1.86: Both server and clients showed the same value when synced. The only time it was not synced was on the server, right after server restart and only for the first 300 seconds. Client side was synced from the start
Groups:
TimeMission InformationMultiplayer

Syntax

Syntax:
serverTime
Return Value:
Number

Examples

Example 1:
hint format ["Synced server time : %1", serverTime];

Additional Information

See also:
time diag_tickTime date missionStart estimatedTimeLeftestimatedEndServerTimesystemTimesystemTimeUTC

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