setDate

-wrong parameter ("Arma") defined!-1.00

LALocalLELocal

Hover & click on the images for description

Description

Description:

Sets the actual mission date and time.

Groups:

Uncategorised

Syntax

Syntax:

setDate [year, month, day, hour, minute]

Parameters:

[year, month, day, hour, minute]: Array

Return Value:

Nothing

Examples

Example 1:

setDate [1986, 2, 25, 16, 0]; //(4:00pm February 25, 1986)

Example 2:

Set real date: //postInit = 1; if (isServer) then { waitUntil {time > 0}; setDate (missionStart select [0,5]); };

Additional Information

See also:

dateskipTimenumberToDatedateToNumber

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

18:52, 6 October 2007 (CEST)

Doolittle

This command is special in that it is "smart". If you add 120 minutes, for example, it will actually advance hours by 2, and so on.

10:00, 7/12/2010 (BST)

Alpha

This command sets the date for the southern hemisphere only, i.e. when the map is in northern hemisphere a date [2010,12,7,17,0] is in day light and and date [2010,6,7,17,0] is in darkness.

21:35, 31 October 2011 (EET)

Osmo

In multiplayer, the effect of this command is local, not global. The date from the server is synchronized with clients when they join the game (including start of the mission and joining in progress). E.g. if this command is executed on server in the init.sqf before the mission starts, every client will be synchronized with server as mission is started. However, if you run this command in the middle of the mission, effect is local.

10 September 2013 (EET)

Killzone_Kid

This command is JIP compatible. Players joining after mission start will get current server date set up.

Bottom Section

Posted on October 4, 2014 - 17:43 (UTC)

MulleDK13

Since an unknown version of ARMA 3, this command now has global effect when executed on the server.

Posted on February 5, 2015 - 06:38 (UTC)

Ozdeadmeat

Arma 3 1.38.128937- Leapyear BUG - setdate [2016,12,31,23,59] yields an ingame date of the 1st of January 2017. If left to tick over from the 30th of December it ticks to 1st January skipping the 31st of December entirely. Feedback_Link

Posted on April 23, 2017 - 02:58 (UTC)

OOKexOo

Regarding execution in the middle of a session, the post of MulleDK13 is not entirely true. If you don't change the year, you are perfectly fine when executing the command on the server only. However, the server does not sync the year. Hence, if you do change the year, you have to execute the command on the server, clients and JIP to account for the missing sync. e.g.
[1986, 2, 25, 16, 0] remoteExecCall ["setDate",0,"JIP_id_setDate"];