[derk]

So there's:

ActionBar.Slot.isReady()

and:

ActionBar.Slot.isActivatable()

What's the difference? They seem to do the same. JDOCS doesn't give me any solution.

There's also a .ready() filter for ActionBar.Slot querying, but not a .activatable(). Doesn't make much sense.

 

[savior]

So there's:

ActionBar.Slot.isReady()

and:

ActionBar.Slot.isActivatable()

What's the difference? They seem to do the same. JDOCS doesn't give me any solution.

There's also a .ready() filter for ActionBar.Slot querying, but not a .activatable(). Doesn't make much sense.

Afaik isReady accounts for abilities on cooldown while isActivatable doesn't?

 

[derk]

Afaik isReady accounts for abilities on cooldown while isActivatable doesn't?

I was told by @Party that this is a bug? So I made a forum thread just in case they forget.

 

[savior]

I was told by @Party that this is a bug? So I made a forum thread just in case they forget.

What i said was rather an assumption based on prior experiences, thus it may be wrong.

 

[slashnhax]

isReady checks that it's activatable and isn't on cooldown.

 

[derk]

isReady checks that it's activatable and isn't on cooldown.

What does isActivatable do then? Or what is its usecase?

 

[tyb51]

I'm experiencing the same issue right now: i think isActivatable checks if the ability is not blacked out on the ability bar?

@Derk Have you found a way to check for cooldown that is not the fixed casttimer cooldown? This seems to be interfering a lot

 

[auxi]

iirc I tested isActivatable with high alchemy on the actionbar with and without runes. Without them it returned false. But maybe my memory is a bit blurry...