wrotation doesnt attack some nightholdbosses

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

you need IDs?

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...

7 hours ago, Rickster said:

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...

 

thats not true for melee characters... ok he uses cooldowns, but doesnt do dps

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.

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

3 hours ago, Rickster said:

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

so it doesnt fully work as range dd as well?

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

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.

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

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

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

Guldan LFR

On 26/03/2017 at 1:47 AM, Rickster said:

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.

 

i agree with you, i just test with the 5 first boss in MM and each time, when the boss go below somewhere 2140M health, rotation begin.

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

true

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

So i confirm it's a bug or whatever you call it because it always happen when you meet the conditions.

i did test all possible options for wrotation (even the advanced one) on 3 differents DPS classes (2 cac and 1 ranged).
i write my own rotations but i also test with some random from the forum and i can say my rotations works everywhere with no problem 

If a Boss had more than 2148M health (full life or not), rotation engine doesnt work and magically begin to work itself when boss's life goes under 2148M. Nothing to do, just wait for it.
It's a heavy problem because in the nighthold, LFR Guldan has more than 2148M and if you are in a 2/3/9 roster, some HM Boss got more than 2148M life and all boss on MM got more than 2148M.

I fear about Tomb of Sargeras, because i believe majority of boss will get more than 2148M life.

So please @Droidz, say something about this, because its a real issue..

Thank you.

I have this same on my Demon Hunter someone know how to fix it?

On 15/04/2017 at 10:26 PM, nevilly1515 said:

I have this same on my Demon Hunter someone know how to fix it?

Actually, only dev can fix this issue, but no response from him since almost a month...
i believe it's not his priority, i saw him take time to answer some issues whom are not a bug on bugtracker but not on this one.
And this one is a real issue, easy to reproduct at 100% rate and could be really annoying especially if you use wrobot for rotation.
Even Rickster in this thread tried to find why this bug happens but still no communication from dev..

he will fix it soon because bugs like that appeared before patch 7.2 too, but as you just said: it is not his priority

best thing to do: use another bot for rotation (there are plenty) or learn how to play your class... i know it is hard to play without mistakes for 5 hours straight but you have to find a solution ;)

2 hours ago, wlhr said:

he will fix it soon because bugs like that appeared before patch 7.2 too, but as you just said: it is not his priority

best thing to do: use another bot for rotation (there are plenty) or learn how to play your class... i know it is hard to play without mistakes for 5 hours straight but you have to find a solution ;)

i'm ok with the fact that is not his priority, i mean , i can imagine the amount of work to maintain something like wrobot.
But just one word from him like this "yea guys i checked it and i confirm its a bug but i have stuff to fix before this" and mark this thread status as "confirmed".
Communication is key here.

I use Wrobot only for rotation so for me this is really problem especialy on mythic raids, if rotation doesnt work correctly this program is crap for me so i want to know when it will be fixed

^ Same here...

Please at least respond to this issue???

If someone can tell me if problem is resolved with the new update.

On 27/04/2017 at 6:03 PM, Droidz said:

If someone can tell me if problem is resolved with the new update.

I confirm it works for Aluriel MM 2899M health (more than 2148M health). ill update when ill fight other bosses.

UPDATE: Works like a charm now !

Thank you @Droidz for working on this issue.

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

EDIT:

Works great now!