Grid2

Grid2

12M Downloads

Bug with "Spell Ready" status when spell has charges

Closed this issue · 4 comments

commented

Description:
Hello,

I noticed that the “Spell Ready” status in Grid2 does not behave correctly with spells that have multiple charges.

Here’s what happens:

  • When I cast a spell that uses charges, Grid2 seems to calculate the “ready” status only at the moment I cast it.
  • If the spell regains a charge afterwards, Grid2 does not immediately update its state.
  • Sometimes Grid2 shows the spell as “ready” while it is still on cooldown, and other times it shows “not ready” even though I have at least 1 charge available.

This makes the “Spell Ready” status unreliable for charge-based spells.

Expected behavior:
The status should track spell availability more accurately by checking the current number of charges (e.g. via GetSpellCharges(spellID)) instead of only using the cooldown.

Steps to reproduce:

  1. Configure a “Spell Ready” status for a spell with multiple charges.
  2. Cast the spell until all charges are consumed.
  3. Wait for a charge to recover.
  4. Observe that Grid2 does not update the “ready” status properly.

Thank you for your work on this addon!

commented

Try out version 2.9.5

commented

Bug description in version 2.9.5

I’m using the Riptide spell from the Shaman class.
I configured Grid to display the buff only when it is missing.
In addition, I added the "spell ready" condition so that Grid should only display the icon if the buff is missing and the spell is ready.

Steps to reproduce

  1. Use all 3 stacks of Riptide.
  2. Remove the buff from myself so that no buff remains active.
  3. Wait until Riptide has at least one stack available again.

Expected behavior

In this situation, Grid should display the Riptide icon (since the buff is missing and the spell is ready).

Actual behavior

Grid does not display anything, even though it should show the icon.

commented

Try out 2.9.6-beta version.

commented

Thanks, I just tested with version 2.9.6-beta and the issue seems to be fixed.
Really appreciate your quick work on this!