Optimization: Revert LoS door check, ClearAreaAroundPosition #704
+22
−89
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
Revert: Checking for door in LoS calculation is expensive and has no benefit, it increase cpu usage. We should take a different approach for this ClearAreaAroundPosition no longer require to be looped since itempickup handle monster blocking properly
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.
Revert:
Checking for door in LoS calculation is expensive and has no benefit, it increase cpu usage. We should take a different approach for this . We have func checkMonsterDamage in attack.go that handle case where we cant reach enemy so its safe to remove it.
ClearAreaAroundPosition no longer require to be looped since itempickup handle monster blocking properly