fix: Replace existing timing with workspace:GetServerTimeNow(), resolve race condition with server creating event after client load #11
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes a timing issue resulting from the use of tick() using local timezones instead of universal time. It also fixes timing issues with os.clock() being different on the server and client from client time drift by using a synchronized time provided by the server.
Additionally this fixes a race condition that causes a client error when the server is slower than the client to require the module.