-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Critical hits on skill use are not reported in notifications #8128
Comments
Is this still an issue? |
Yes, this is still an issue. Note to anyone working on this, currently you can't see how much boss damage you do from notifications due to #11828 but you can watch how your test account's I've removed some old comments from this issue (just requests to work on this and confirmations/questions related to them). |
is this still an issue ? would like to work on this |
@HerrMoriden You have a couple of other issues assigned to you so we'll keep this one open for someone else to work on. When you've finished the other issues, post again here if you'd like to claim this one. Please see this comment from Matteo about claiming just one issue at a time. |
Hi, does this still need to be implemented? I looked into the code and I think I'd be able to implement this. Let me know if I can help. |
@lstanford53 Feel free to take this on! Thanks! |
Sure, I'll start on it now. |
@CuriousMagpie Hello, I have opened a PR that fixes this issue. Here's the link: #14696 |
General Info
Description
It is possible to score a critical hit with actions like Brutal Smash, lending a modest boost to the damage done to a boss. However, unlike critical hits when scoring tasks, there is no feedback in notifications that this has occurred. In the past, this was difficult to notice, but now that we have immediate output of boss damage, it's clear that sometimes you randomly get more progress without any indication as to why. We should fire the critical hit starburst including the relevant bonus amount when landing skill crits.
Console Errors
None
The text was updated successfully, but these errors were encountered: