Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ward killer #24

Merged
merged 8 commits into from
Oct 21, 2018
Merged

ward killer #24

merged 8 commits into from
Oct 21, 2018

Conversation

evaldobratti
Copy link
Contributor

basically rebases #3 and fix build errors

remove old ward processor in favor of the new one

micael.bergeron and others added 8 commits October 14, 2018 14:47
this processor may be used to track down warding events, such as
Counterwarding, Placement or Expiry. It uses the combat log events
correlated with entity life state tracking.
this processor may be used to track down warding events, such as
Counterwarding, Placement or Expiry. It uses the combat log events
correlated with entity life state tracking.
upon a same-tick event, there is a chance that the ward kill will be credited to the wrong attacker, but this commit limits the impact of this caveat by separating the wards from the sentries.

thus you will always be credited a ward kill if you last hit a ward
@howardchung howardchung merged commit b817f8e into odota:master Oct 21, 2018
@howardchung howardchung mentioned this pull request Oct 22, 2018
@howardchung
Copy link
Member

I'd like to get this back in when we find the issue causing parses to fail. Maybe there was another step required to use the new processor that wasn't checked in?

@evaldobratti
Copy link
Contributor Author

I couldn't debug what happend yet, as soon as i can I'll give a report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants