OS.date requires more information

[railworks2]

As a result of finding this bug

OS.date is inconsistent in studio vs in game

When using os.date in game vs in studio, it prints conflicting information. For this bug, we’ll be using the code print(os.date("*t").hour) We expect this, will print the hour of the UTC time standard/GMT; across all platforms. Studio does not do this, it uses the local timezone not UTC. We expect as the os.date API says that if a time is not given, it will use os.time which uses UTC while (as an example) tick() uses the local timezone of the client.

Bug repo in multiple environments

In game …

We found that the OS API page, at least in context of os.date() needs some extra information to explain the difference os.date(“!*t”) and os.date(“*t”)

This information is that the use of the “!*t” caused it to be UTC while just “*t” used local time. This should be clearly noted there on the page.

[Ozzypig]

Sorry for the frustration this must have caused - I’ve noted this behavior on the page. It should be visible by the end of the week.

[railworks2]

There has been no update to this document.

[Ozzypig]

Whoops. It looks like the presently visible page is a cached version - I’ve put in a request to have the cached version cleared so the fix is visible. Give it one more day or so.