Merged
Conversation
Entity can now have a tick's cooldown before sending there updates, avoiding client overload with data update that could be delayed
azeloup
approved these changes
Dec 13, 2025
Vierre3
requested changes
Dec 14, 2025
Owner
Vierre3
left a comment
There was a problem hiding this comment.
- Remove unused getSize method from ECS registery
- Refactor main loop because tick rate was already handled in window.need_refresh call
- when there was a kill packet sent by the server got lost, the client crashed when a new entity packet was send at the position of the dead entity. The override freeing a std::queue caused the crash
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Entity can now have a tick's cooldown before sending there updates, avoiding client overload with data update that could be delayed
CLOSES #121