Page MenuHomeFeedback Tracker

"year" doesn't sync when setDate is used on server restart
Assigned, WishlistPublic


If you setDate on server restart on the server the year will not sync not immediately not for JIP clients.


Legacy ID
Steps To Reproduce

put this in init.sqf

if (isDedicated) then {
setDate [2000, 1, 1, 0, 0]
} else {
waitUntil {time > 0};
hint str date

start dedicated, join

hint shows: [2035, 1, 1, 0, 0]

Event Timeline

Killzone_Kid edited Additional Information. (Show Details)
Killzone_Kid set Category to Engine.
Killzone_Kid set Reproducibility to Always.
Killzone_Kid set Severity to None.
Killzone_Kid set Resolution to Open.
Killzone_Kid set Legacy ID to 1883712293.May 7 2016, 5:08 PM

This should be pretty simple fix. I would even settle for "acknowledged" at this point :)

Still not fixed. Year is always 2035...Really?

note: this may cause issue like moon position/phase differs and star position differs (not sure about sun, prolly too)

I predict if this ticket left open for 21 years, the problem will go away by itself.

ok so the bug is in the setDate when executed on server

JIP will also get 2035 even though the server is running 2014 for example. I think the 2035 value is default value set in mission.sqm

I predict if this ticket left open for 21 years, the problem will go away by itself.

Only 19 years left!!!

2600K added a subscriber: 2600K.Apr 4 2019, 10:48 PM

Typo in the script, only a few years to go!

16 years, we are getting closer!

JIP year should be fixed in the next dev, changing date in the middle of the mission will require remote exec due the command having local effect