Mavmins' Destruction Warlock

[billybuffalo]

Works better now. Testing on heroic hof right now.

[LazyRaider]

Ok so I haven't been watching my pet too much during raids

but does this profile leave the pet on the boss, or does it change up the pet attacking when you switch targets?

If so can we have an option to have pet only attack the boss we are targeting (or focused on "other than Magera") and not adds? Having a Observer travel is lost dps, although most fights now don't need observer (atleast how I play and sim out).

Will test the new profile when I get time.

[billybuffalo]

not sure what happening but on Blade lord after he gets below 20% the profile will hang for a sec and i have to just start mashing buttons to get it going again. I did lower the wait time for DS but not sure if that would screw it up... shit happened to fast to see what variables where there to screw it up.


edit:

Dont know if this helps

40x <string>:"local Targethealth = 100 * UnitHealth("targ...":29: attempt to compare nil with number
<string>:"local Targethealth = 100 * UnitHealth("targ...":29: in function "?"
<string>:"if PQR_Addon_Loaded == nil then...":765: in function "PQR_NextAbility"
<string>:"if PQR_Addon_Loaded == nil then...":534: in function "PQR_ExecuteRotation"
<string>:"if PQR_Addon_Loaded == nil then...":287: in function <string>:"if PQR_Addon_Loaded == nil then...":214

[Mavmins]

The pet doesn't have any specific behaviours, not sure how to make it only attack boss but ill certainly look into it
Thanks billybuffalo ill look at the shadowburn code a little later tonight and see if I can reproduce that error and fix it

[Phishstick]

The pet doesn't have any specific behaviours, not sure how to make it only attack boss but ill certainly look into it
Thanks billybuffalo ill look at the shadowburn code a little later tonight and see if I can reproduce that error and fix it

You do not need to make any changes to the pet. Putting your pet on passive and the using the Attack (not assist) button will keep the pet on whatever target you set it to attack
when pet is on assit it will switch to whatever target you dps.

[billybuffalo]

Yeah the pet is no issue here

[billybuffalo]

The pet doesn't have any specific behaviours, not sure how to make it only attack boss but ill certainly look into it
Thanks billybuffalo ill look at the shadowburn code a little later tonight and see if I can reproduce that error and fix it

The error i got completely crashed pqr. Havent been able to reproduce it though.

[billybuffalo]

Question, in bug grabber if u hit the report bugs button, who does it go to?

[Mavmins]

No idea where it goes, I wouldn't send it !

I've tweaked the beta so please redownload it, update wont work. Im going to guess that when you got the error you had a focus target ?

[Captncrunch]

Question, in bug grabber if u hit the report bugs button, who does it go to?

Probably Blizzard, and I assume if they see the lua error they will know you are using a bot.

[billybuffalo]

No idea where it goes, I wouldn't send it !

I've tweaked the beta so please redownload it, update wont work. Im going to guess that when you got the error you had a focus target ?

No focus target

[billybuffalo]

As far as the send report button, i did push that ****in thing. I meant to push todays report button and hit that stupid thing by mistake.

Well if i get banned ill have to tell them why i really use pqr. Only have 1 arm.......

Edit:

BugSack eases the process of capturing bugs. It captures information about Lua errors that occurred during your play session, including the full debug stack. It aims to be invaluable to developers, and a useful tool for advanced players that use beta-quality addons.

BugSack includes a LDB data broker plugin that displays the last 5 errors in the tooltip. It can also bring up a frame to display all other errors for the current session, or for any other session. The text of the error can then be copied & pasted to a source outside of WoW (for example the forums) so that other developers can determine what's at fault.

Errors can also be sent to another player that has BugSack installed, if you know someone that can help you interpret and resolve the errors in your interface.

Remember to file a ticket if you find a problem or want to request a feature. If you want to help translate BugSack, you can do so at the project page on wowace.com. Thank you!

!BugGrabber

The addon has a hard dependency on !BugGrabber, which is the addon that actually grabs the bugs. !BugGrabber is intentionally kept small, and it does not use any libraries, to make sure that any errors in those libraries do not mess up the system.



So it doesnt go anywhere if u dont configure it.

[billybuffalo]

Ok, there is def something going on with the shadowburn logic.... soon as a boss or target gets to 20%, it stops and I have to spam shadowburn myslef.

[billybuffalo]

Since I am guild raiding tonight, I will go back to using the last version for tonight. I cant afford to lose dps tonight. Ill go back to trying to figure out what is causing this tomorrow.

[billybuffalo]

Itr absolutely does have something to do with shadowburn. verified that on a nalak kill. since he takes awhile to die. plenty of time at under 20%. As soon as I have 1 ember and target is under 20% it will not cast shadow burn. If I spam shadowburn, and have no embers, it will pick back up with rotation, until I get 1 ember. then stops again.