Both tick() and os.time() return the number of seconds since the unix epoch.
Small difference, tick() returns the number of seconds since the unix epoch from the local session’s computer.
os.time() returns the number of seconds in Universal standard time still using time elapsed on the local session’s machine. So this just accounts for timezones; tick() will not.
So if you’re syncing multiple machines (server and client), use os.time.
Edit: If two machines do not have synced time and date, this will not work.
This will give you the ping of the client. When you get the ping, simply do what you want to do but account for the ping loss. For example, if the ping was 100ms(0.1 seconds), you would fast forward what you would be doing by 0.1 seconds to account for the delay.
Yeah normally i send a time() on remote events from spells to get the Delay that had, so i calculate the Delay and make the the predicts, but as i saw time() on client and on server return different values, i dont know if i need worry about that difference between server and client time ()