Alternatives To tick()?

[Mortai_Yt (xM_MORT)]

I have heard that tick() is being deprecated sooner or later, so I have tried avoiding using it. I am now in a situation where I need an alternative to tick() and I have no idea on what to use.

I have tried:
os.time() - No decimal
os.clock() - Not based on UNIX epoch and also not efficient

So, what is an alternative to tick() that functions in the same way but will not be deprecated? (I am fine with creating my own function if I have to, I would just like to know how)

Thanks!

[DasKairo (Cairo)]

You would be looking at os.clock() for something similar, essentially functions the same way (at least in what its mostly used for in math) but its more precise, and based on the CPU time.

os.time() would the closest to tick(), but without decimals, and based on UTC time, rather than Device local time like tick().

Those are the MAIN alternatives you can use.

You can also use DataTime.now() for decimals, however its not as precise as others, only going to the thousandths place.

[SomeFedoraGuy (rusuRares)]

@Mortai_Yt

I have heard that tick() is being deprecated sooner or later, so I have tried avoiding using it.

Really? Where have you heard that? tick() should not be deprecated.

[Mortai_Yt (xM_MORT)]

Luau Recap: June 2020

… otherwise known as “This Month in Luau” I guess? You know the drill by now. We’ll talk about exciting things that happened to Luau - our new language stack. anxiously glances at FIB3 thread that casts a huge shadow on this announcement, but hopefully somebody will read this Many people work on these improvements; thanks @Apakovtac, @EthicalRobot, @fun_enthusiast, @zeuxcg! If you have missed previous large announcements, here they are: Faster Lua VM Released Luau Recap: November 2019 Luau …

says tick is going to be deprecated in the future.

[Mortai_Yt (xM_MORT)]

@DasKairo

You would be looking at os.clock() for something similar, essentially functions the same way (at least in what its mostly used for in math) but its more precise, and based on the CPU time.

os.time() would the closest to tick(), but without decimals, and based on UTC time, rather than Device local time like tick().

I basically wrote this already:

@Mortai_Yt

I have tried:
os.time() - No decimal
os.clock() - Not based on UNIX epoch and also not efficient

But thanks for the extra detail.

@DasKairo

You can also use DataTime.now() for decimals, however its not as precise as others, only going to the thousandths place.

Do you mean DateTime.now() ? Anyway, this doesn’t seem to have a decimal for me when I print it to the console.

[debugMage]

Use DateTime.now().UnixTimestampMillis / 1000.

[Mortai_Yt (xM_MORT)]

Sounds great, can you explain how this works?

[debugMage]

From my understanding, it’s a “more accurate” version of tick(), or better said: a better version of it. If you need even more decimals you can use workspace:GetServerTimeNow().

No idea why they all give slightly different numbers unfortunately, but I assume they’re a replacement for tick() for the reasons given in the thread you linked.

[Mortai_Yt (xM_MORT)]

workspace:GetServerTimeNow() and DateTime.now().UnixTimestampMillis / 1000 both sound great, thanks! I believe they return a different result than tick() because tick is based on your current timezone. Is there any way to adjust these values to my timezone? (Or whoever is playing’s timezone), if not that is fine, at least they return decimals and are similar to tick.

[debugMage]

DateTime.now() supports changing timezones.

I’m not entirely sure how to do it since I’ve never done it before, but the documentation mentions it’s possible.

[Mortai_Yt (xM_MORT)]

Alright, I will try. Thank you!