Essence forecast issue impacting recommendations based on 'time_to_max'
W8ink opened this issue ยท 8 comments
Before You Begin
- I confirm that I have downloaded the latest version of the addon.
- I am not playing on a private server.
- I checked for an existing, open ticket for this issue and was not able to find one.
- I edited the title of this issue (above) so that it describes the issue I am reporting.
- I am reporting an issue with the default priority included with the specialization (imported or edited priorities are not supported).
WoW Version
Retail (Dragonflight)
Describe the Issue
Issue in essence tracking when essence >= 4 . same with essence.time_to_max it stuck on 4 sec.
How to Reproduce
- Enter game as Dev Evoker.
- Spend essence.
- Watch state of essence.time_to_max
Talent Loadout
BsbBAAAAAAAAAAAAAAAAAAAAAAIAAAAAAgWIJikQgEJlkkASLgESSAJJSESSC
Snapshot
Raidbots Sim Report (Link)
No response
Additional Information
No response
Contact Information
W8ink#7189
Thanks for the report. I am testing a solution for this now; fundamentally, the problem is that the base UI does not give information about progress as Essence regenerates. I mostly have it solved now and will post in the next release.
This should be addressed in the latest release (10.0.2-1.5). Let me know if you are still seeing issues.
This should be addressed in the latest release (10.0.2-1.5). Let me know if you are still seeing issues.
the issue remains. its hard to explain what exactly happens.
lets begin from where issue appears.
when i have 0 essence its ok with essence.current but essence.time_to_max doesn't work properly.
when i have 3 essence all conditions work as it must work
when i just get 5 all contitions show wrong values.
10.0.2-1.5 fix did not solve the problem completely.
That's all I have at the moment.
since English is not my native language somewhere I could not correctly express my thought.
In the wake of another ticket, I'm making modifications to the options UI so that those preview tooltips will have more accurate information. In some situations, the game state wasn't being reset before generating the preview. This could impact current Essence and time_to_max as well.
@W8ink Thanks for more information.
1st screenshot is actually fine. When it'll take longer than the allowable window for the addon to make a decision, resource forecasting just assumes things aren't going to happen. That's where 3600 comes from. Going from 0 to 5 is simply longer than the threshold the addon needs to care about.
2nd screenshot differs because the time it takes to go from 3 to 5 is within the period of time the addon cares about.
3rd screenshot is interesting. You can't trust the UI at some times. First, I'm going to assume you changed talents so that you actually do have a maximum of 6 Essence, since that's a change from the prior two screenshots and you didn't mention doing that. However, the animations in the default UI for Essence regeneration are also misleading.
Example:
In this GIF, I spent two Essence, then I allowed Essence to partially regenerate so that the 5th Essence is about halfway full and spent Essence again. Essence drops to 2 -- the half regen doesn't show in the UI -- but when third Essence halfway regenerates, it suddenly snaps to full.
So tell me the impact here. What impact to recommendations are you seeing since 1.5 released that appear incorrect? In order to calculate Essence regeneration, I have to track the time that Essence starts regenerating in a way the UI itself doesn't provide. Let me know (with snapshots) if/when you see actual recommendations that appear wrong. Unfortunately, we can't rely on the default UI elements to be accurate about Essence regen.