Hekili
commented
3 years ago Please provide the required ticket information:
BEFORE SUBMITTING AN ISSUE:
-
Check to see if you are using the latest version of the addon. If there is a newer alpha/beta/release version, see if your problem exists with the new version.
-
Check to see if someone else has already opened an issue report here. Please don't submit repeat reports.
Describe the Bug/Issue A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
WHEN SUBMITTING AN ISSUE:
Please provide the following information. Leaving it out may result in your ticket being ignored (because I won't have the information needed to explore your report).
- The information from the Issue Reporting tab ( /hekili > Issue Reporting ). This provides your talent and gear information. You can paste it to pastebin.com and provide a link here.
PUT ISSUE REPORT LINK HERE:
- If reporting a disagreement with the addon's recommendations, please take a snapshot when you observe the issue and provide the snapshot. This is not a screenshot. A snapshot can be generated by binding the Pause feature on the Toggles tab. When you press Pause, a snapshot of how the addon decided on its CURRENT recommendations is generated and saved to the Snapshots tab. Copy and paste this to pastebin.com and provide the link here.
PUT SNAPSHOT LINK HERE:
- If reporting an error (i.e., the addon freezes and/or disables itself), please install the BugSack and BugGrabber addons as they will enable you to paste the exact error message, with detail that will help me identify where the code error is located. You can paste the error information here or use pastebin.com for that as well.
PUT ERROR MESSAGE(S) HERE:
enjioh
Zarggg
Specific Scenario: I'm in a multi-target (3+mobs) fight, and I open normally with wrath, wrath, dots, celestial alignment, Convoke. Convoke gives me a Starfall, and I'm either Astral Power capped, or close to cap.
At this point, Hekili, sensing that I'm AP capped, will suggest Starfall, even though I have a relatively fresh Starfall from Convoke, and I'm still early in the Eclipse from the Celestial Alignment. At the moment, I override the suggestion with a Starsurge to drop AP and buff my Eclipse.
Request: Can someone look into the logic for Balance and perhaps adjust the Starfall recommendation to check for whether starfall is already running OR the current Eclipse is long enough to build enough AP to get another Starfall before it ends? This is tricky because if you don't Starfall in the above scenario (and SS instead), AND don't generate enough AP to get another Starfall before the Convoke one runs out, you lose dps. So the new trigger has to be aware of "how long the current Starfall has remaining AND if we will have enough AP to starfall in X seconds when it runs out"
Suggestion: update the recommendation so that "if current Astral Power is ~90-100 AND Starfall has 5+ seconds remaining, suggest Starsurge". this way, you still starfall most of the time, but in the above scenario, where you'll be able to SS after the convoke, and easily wrath 2 more times after to get 12 AP, you can sneak in a SS for additional dps.