Client tick() being far ahead of server tick() when FPS is unlocked?

[NexusKorthos]

So im making a remote cooldown script and client has to send its tick() to the server for comparison with its tick(). One of the checks is if the received tick() is not higher than server tick().

This is the result when im in studio (60 FPS):

Client tick(), Server tick(), Server tick - Client tick

The difference is only 0.015 which is normal, and now in the game with unlocked FPS:

Client tick(), Server tick(), Server tick - Client tick

The client tick() is over 3500 ahead of the server tick() and the gap is not always consistent.

I want to use tick() for hitreg in the future and with this problem i dont know what to do. Ive heard some people used this technique in their games, so does anybody know what to do?

[sjr04 (uep)]

tick() returns the seconds passed since January 1, 1970 but in local time. So you are passing the tick() from the player’s timezone and using it against the server’s timezone.

os.time() should be used here instead; it returns seconds in UTC time since January 1, 1970 and can guarantee consistency. Plus tick() is going to be deprecated in the future.

[RVVZ (Emperor)]

Sync tick() for client and server

Hi, I’m currently working on a game that works with CFrame:lerp() and I have to calculate the time difference dt. The server sets a StartTime and then server and client can calculate dt accurately. The problem is I use tick() for StartTime, but if the client isn’t in the west coast time zone, the client gets a different output from tick()… For some reason when I use time() the game is 3 times as laggy as using tick(). I also tried os.time() + tick()%1 (since os.time() only gives integers), but …