Is there any real difference between os.time() and tick()?

[Ethanthegrand14 (Ethanthegrand)]

Its pretty self explanatory.

Is there any real difference between os.time() and tick()?

Thing is when i run this code:

print(tick() ..  " / " .. os.time()) 

The results between tick and os.time are pretty similar.

The only noticeable difference is that tick has decimals.

Is there more i should know about these two functions?

[DrKittyWaffles (x64dbg)]

tick uses the current time zone.

If you look at your image, os.time and tick are actually returning two different nubmers.

tick being the seconds since EPOCH in your time zone, os.time returning Unix time since EPOCH.

[sjr04 (uep)]

tick() gets the amount of seconds (+ milliseconds) from 1/1/1970 but in local time.

os.time() only gets the seconds (not milliseconds) from the same date but in UTC time.

@zeuxcg

• tick() sounds perfect - it has a high resolution (usually around 1 microsecond), and a well-defined baseline - it counts since UNIX epoch! Or, well, it actually doesn’t. On Windows, it returns you a variant of the UNIX timestamp in local time zone. In addition, it can be off by 1 second from the actual, real UNIX timestamp, and might have other idiosyncrasies on non-Windows platforms. We’re going to deprecate this in the future.

So, if you need a UNIX timestamp, you should use os.time() . You get a stable baseline (from 1970’s) and 1s resolution. If you need to measure performance, you should use os.clock() . You don’t get a stable baseline, but you get ~1us resolution. If you need to do anything else, you should probably use time() .

Roblox engineers have plans to deprecate tick()

[rogeriodec_games]

I’m starting a function to store possible game errors in a DataStore to later analyze them and fix bugs.
For that, I’m using LogService.MessageOut
I need to store the time when the error occurred, exactly as it is shown in the Console today, ie plus milliseconds.
os.time() does not show milliseconds.
os.clock() is not based on the UNIX epoch.
tick() would then be the only viable solution, similar to os.time() but including milliseconds.
But they are saying that tick() will be deprecated.
So what’s the solution to storing UNIX epoch with milliseconds?

[Lemoneese]

DateTime, specifically DateTime.now(), gives the number of milliseconds since the UNIX epoch and already takes into account for times zones (so it’s in GMT time).

[onlinefeladatok (Pro_menChairman)]

why are there so many time counters