[REC] trinket.t2.cooldown.remains always returns 0
syrairc opened this issue ยท 1 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).
Describe the Issue
Per my comments in #pack-development channel, trinket.t2.cooldown.remains seems to always return 0. This means certain trinkets are never recommended if they rely on your other trinket to be on cooldown.
In the example provided, I'm on an augmentation evoker with Belor'relos in trinket slot 1, and Balefire Branch in trinket slot 2. Belor'relos will not be used unless trinket 2 cooldown is > 20 seconds (or one of the other conditions are met (they aren't in my example.)
In my example there are two snapshots, the first one is balefire in trinket slot 1, belor'relos in trinket slot 2. Using balefire and then following the rotation will result in belor'relos being recommended when we're in the GCD.
The second snapshot has belor'relos in trinket slot 1, balefire in trinket slot 2. Following the same process, putting balefire on cooldown and following the rotation, belor'relos is never recommended. You can see in the snapshot and in the tooltip ingame that trinket.t2.cooldown.remains is always 0. trinket.t1.cooldown.remains works as expected.
How to Reproduce
- Equip on-use trinket in trinket slot 2
- Use trinket 2
- Observe return value of trinket.t2.cooldown.remains
Snapshot (Link)
Raidbots Sim Report (Link)
No response
Additional Information
No response
Contact Information
No response
