Problem - Target.Slowed.SlowPct returns null rather than 0

[AmericanNero]

If you attempt ${Target.Slowed.SlowPct}, and the mob has not yet been successfully slowed, it returns null. Shouldn't it return 0? If you try ${Target.Slowed.SlowPct}<70.... you can't do it because null is not an int so it craps out.

Workarounds to be able to compare int...

/declare SlowPct int local 0
/varcalc SlowPct ${Target.Slowed.SlowPct}+0

One can also do (${Target.Slowed.SlowPct}+0) as part of a condition within an ini.

Anyhoo...

 

[ChatWithThisName]

Try wrapping it in an ${Int[${Target.Slowed.SlowPct}]} and see if that produces the result you're looking for?

 

[dannuic]

Target.Slowed will be null if there is no slow, so anything that flows from it will also be null. It's best to test for null as well as 0.

 

[AmericanNero]

How would I detect null? Target.Slowed.SlowPct returns type int when it has a numeric value, otherwise null. I tried a variety of ways. The only way that captured the state in adequate fashion was adding 0. Are you suggesting ${Target.Slowed.Equal[null]}? It still does not address that a type int returns null instead of 0, and one cannot compare null to int.

 

[Many_Whelps]

Make it a multi variable condition

!${Target.Slowed} || (${Target.Slowed} && ${Target.Slowed.SlowPct}<70)

 

[AmericanNero]

I got this crazy idea that its fixed in mq2 so we don't have to have excessive conds!~

 

[Blasty]

/if ( ${Target.Slowed.SlowPct.equal[null]} )

 

[Knightly]

NULL and 0 are both false. You don't have to specifically test for it unless you specifically want to know if it's null, but automatically converting it to int would lose the capability to test for when it is null.

 

[ChatWithThisName]

I got this crazy idea that its fixed in mq2 so we don't have to have excessive conds!~

Feel free to submit your proposed changes for review.

 

[Dragonslayer]

None of the solution provided worked, but the one from @ChatWithThisName : ${Int[${Target.Slowed.SlowPct}]}<70
Works wether or not target is slowed for me

 

[exspes007]

check for a ${Target.Slowed.ID} first. if thats valid, then check your %.

 

[Dragonslayer]

check for a ${Target.Slowed.ID} first. if thats valid, then check your %.

For which benefit? If I can find no condition where the solution doesn't work, adding further checks/calculations will only add workload, isn't it?

 

[Hylander]

Better yet, dont worry about it. The percentage slow is mitigated in the calculations anyway, so you aren’t getting the headline number. Have a race to see who gets a slow on the mob, and be done with it. (Belt, chanter, counterbias, turgurs, beastlord).

Shaman AA slow is great, because while it is cast, there is no GCD, so your spells are instantly available for the next cast. Greatly improves Shaman efficiency

 

[Dragonslayer]

Shaman AA slow provides an additional casted cripple as well.

@Hylander : not shure if I understood your first sentence. ${Int[${Target.Slowed.SlowPct}]} shows the numbers of the spell, not the real effect on mobs. So this should do, whats supposed to do.
If ther's a slow applied as good or better than mine, skip my slow.

 

[AmericanNero]

After reading the replies and going through the code, I believe I see how it works now. MQ2 itself is only concerned with exposing the gamestate, not crunching it further. Got it! Now that is settled, I think I will go through the KA12 doc and add some suggested conditional tests so I don't forget any details.