Improved fast moving entity optimization for void cannons. #167
Conversation
This file contains 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.
Why is this optimization needed?
I was encountering an issue with a 360 degree void cannon (which shoots a pearl to the world border in 1gt), the server was crashing whenever I tried to shoot, due to watchdog. I looked at the crash report stack trace and discovered how poorly optimized the entity collision search is for entities which have a very high velocity, making the cannon unusable without this fix.
How does this optimization work?
this optimization works by only searching for entities in chunks that the pearl (or any entity traveling fast enough), would actually travel through.