Rickster

Correct, and that is how I have it set. The issue (I think) is that training dummies are not hostile by default, they are neutral. You can attack them, and the rotation starts and continues as expected after you attack them.

The issue is that I cannot use them for testing AOE rotations were I have set "hostile unit near target" conditions because it will not detect numerous hostiles because they are neutral by default. If it could just treat all dummies as hostile, the issue would dis-appear? I hope that makes sense?

Thanks!

It does not, I confirmed this on my druid.

I developed this as a LUA condition to resolve it:

====================================

local name, rank, icon, count, debuffType, duration, expirationTime = UnitBuff("player", "Savage Roar")

if not expirationTime then 
   retVal = 1 
else 
   timeLeft = (expirationTime - GetTime()) or 0
   if timeLeft < 5 then 
      retVal = 1 
   else 
      retVal = 0
   end
end

====================================

This returns 1 when no Savage Roar buff, or it is about to expire (within 5 seconds) other wise it returns 0

return value var = retVal

return value research  = 1

Woot! TY. I am about to run some heroics, I'll report back...

EDIT:

Works great now!

^ Same here...

Please at least respond to this issue???

On 4/2/2017 at 5:21 AM, Sonat said:

So, its almost two weeks now this issue has been submitted, no words from dev and it began to be a real problem for me (and for some other users too i believe) because i use wrobot almost exclusively for rotation.
Don't get me wrong, i like Wrobot and Droidz but if we can have some news about this issue, it will be great.
Thank you

agreed

On 3/23/2017 at 5:38 AM, Droidz said:

Hello, any mob easy to find/join with this problem?

Guldan LFR

Could it be that the underlying code is using an long integer somewhere that tracks the targets health? And exceeds the 2147483647 max value for C#?

https://msdn.microsoft.com/en-us/library/296az74e.aspx

Perhaps initializing the var with UInt32 instead of int32? All speculation on my part...

https://msdn.microsoft.com/en-us/library/x0sksh43.aspx

OK, just ran 2 wings and Guldan in LFR. It looks like the rotation will not start until the Boss reaches 2,140,000,000 health. That is as close as I could get watching the numbers roll down anyway.

Botanist = 2194M health - didn't start until a few seconds after pulling (saw it start right around 2140M)

Guldan - same thing (not sure what his starting health is)

Star Auger = 2140M health - started right away, but I remember having to wait in heroic last week (and the weeks before)

All the other bosses I tried started below 2140M and I had no trouble with any of them.

wlhr, that is correct. I will try to make a list of NH bosses this does not work on on my next raid night. I have attached my FightClass profile for reference

ricks_BM-legion.xml

19 hours ago, Sonat said:

Hi guys my 2 cents here as a melee class:

For Gul'dan on LFR/NM/HM: Rotation didnt work at the beginning on guldan, but working on the three mini boss (inquisitor etc etc).
When you reach P2 : rotation didnt work on gul'dan but works on eyes. after hitting some eyes, rotation begin to work on Gul'dan. when rotation begin to work on gul'dan, it will work for all the remaining fight.

For Botanist: Rotation didnt work at the beginning on Botanist, but working on the spawned flowers. after hitting some flowers, rotation begin to work on BOTA. when rotation begin to work on BOTA, it will work for all the remaining fight.

That coincides with my 66% estimate. That is about the time P2 always started for us. Just another data point, I'm am a ranged class (BM hunter) and I use health percent conditions in my FightClass profile

Guldan for sure. I just got out of our Heroic Guild run. It starts working after he reaches 66% health for some reason. I noticed the same thing with some other bosses in NH, after they lose a certain amount of helth, or the fight reaches a certain point Wrotation starts working normally again. Adds are not a problem...