Why should "tick()" be avoided even tho It provide Milliseconds precision?

[LucieKitsuneko (LucieKitsune)]

I was messing around with the time functions (os.clock, os.time, etc) and realised tick() was the only one with milliseconds precision based off the UNIX time, os.time is also based off UNIX but doesn’t return millisecond precision, now I needed precision on an UNIX timestamp, so naturally I would need to use “tick()” but i’ve heard it should be avoided, is there any counter part then?

[Godzilla_RealLife (coolrobloxplayer)]

Stated in this image it can be inconsistent

[Bigmancozmo (BMC)]

From Using tick() for handling time systems - #8 by sleitnick

@sleitnick

The general rule is to not use tick() for anything anymore. There are a couple issues with tick:

1. It may be up to 1 second off
2. It is relative to the current system time (i.e. timezones affect it)
3. Likely to be deprecated in the future

[EmilyBendsSpace]

As long as you’re only using tick() to compare to values from other calls to tick() on the same machine, there’s no problem. It’s fine for implementing timers or measuring elapsed time. Just don’t use it as an absolute reference for time or compare values from tick() calls made on different machines.

[Yarik_superpro (The_GrandOptimizer)]

use workspace:GetServerTimeNow() for sync offset towards os.clock()
That it
The most optimal setup imo
Sync offset every ~5 minutes