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

Possible root of 4-heart bug. #71

Open
kksym opened this issue Mar 29, 2016 · 5 comments
Open

Possible root of 4-heart bug. #71

kksym opened this issue Mar 29, 2016 · 5 comments

Comments

@kksym
Copy link

kksym commented Mar 29, 2016

https://github.com/Civcraft/Humbug/blob/master/src/main/java/com/untamedears/humbug/Humbug.java#L1761

ignoreCancelled = true

Possible cause of the 4-heart bug? If under a certain condition the event is cancelled (doesn't appear to ever be cancelled in Humbug however) and the event is uncancelled after the strength reversions were supposed to apply, presumably the damage would be vanilla. I have no idea which plugins may fiddle with EntityDamageByEntity events (possibly NoCheatPlus/CombatTag/private server-side anticheat thingy), but unless I'm missing something very obvious, it seems plausible.

@ProgrammerDan
Copy link

Hmm, so as LOWEST priority this event would only potentially be superseded by another plugin having the same event trapped at also LOWEST priority.

More likely is that another plugin is overriding the changes Humbug is making here then that Cancelled is involved (as when this is called, again, it is unlikely any other handler has been called, so the event will never have been cancelled).

This due to Bukkit running events in reverse priority -- LOWEST is first, MONITOR is last.

@Diet-Cola
Copy link

Seen here at 52:52

Go from 7 hearts down to 3 hearts on one hit.

@ProgrammerDan
Copy link

Wish I knew exact date and time on that (in server timezone) so I could pull the 2.0 logs and see if anything pops up on console (exception, etc).

@Diet-Cola
Copy link

‎19 ‎September ‎2015, ‏‎00:45:29 GMT was the time the video was recorded.

Given that the video would of finished, the event happened 50 minutes from the end meaning at roughly 18 September 2015 11:55:00 GMT is a rough idea.

@ProgrammerDan
Copy link

I'll see what I can find / have access to.

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

No branches or pull requests

3 participants