Open
Conversation
Contributor
Author
|
Updated after discussion with gigamonster offline |
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.
Updated tracking for what's considered recent damage:
RecentDamageTakencould discard damage prematurely, it didn’t account for future EMP freeze ticks preventing us from recovering an instance of damageGetRecentDamageTaken()should now always represent all instances of damage that are the reason for a player's energy being below full health. If a player is at full healthGetRecentDamageTaken()will return an empty listAdded impact of EMP bombs to damage dealt and taken stat accounting
CalculateDamageSources(), the recharge that's prevented by an EMP is counted as damage taken/dealtUpdated ForcedRepel counting and attribution