What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

Superbad 4.0 (Druid Routine)

Status
Not open for further replies.
Handnavi

I recently looted a heroic Rune of Re-orgineration. Does that buff account for applying the more powerful dots. I'd like to see rip line up with a DoC+TF+SR+Trinket Proc ONLY. BEcause if I play my dps perfectly I'm looking about 30% of total dammage coming from rip. Manual play I see pretty high rip % but with this, I'm seeing rake and rip =. Its kinda a wierd but is there any plan to add a option box to account for the rune proc?

It takes ror into account. It uses rake often instead of mangle/shred.
 
Superbad calculate the damage of Mangle as 5*weapon damage + 390 * 1.3 if DoC buff is on. I am wondering why it is not (5*weapon damage + 390)*1.3 . I think I have to try the dummy.

edit: After dummy test with only a weapon equipped, it can be confirmed that the formula should be (5*weapon damage + 390)*1.3.

Thanks for this wonderful bug report. Will fix it. :)

Edit: i've looked into it now and i have to say, that the formula is correct as it is.

The weapon damage is allready multiplied by our damage multipliers when we grab it from the server, the 390 not. :-)
 
Prepare for a new update...

- fixed the lag issues
- more cool stuff
- :)

Will hopefully upload it today
 
Bot has stuttering issues upon engaging (moving to target)

When the bot acquires a new target the following events happen:

1. Faces target and cat forms
2. Walk towards target
3. Begins combat

Here's the problem with #2, 80% of the time, my druid almost always tries to go behind the target (I can see the bot is clicking behind the target - directly opposite wherever the mob is facing) while also trying to move towards him in a bee-line fashion (similar to right-clicking a mob directly with click-to-move on). So basically it alternates between the direct and behind-the-target clicking every 0.1s, thus the stuttering, until he goes within melee range and everything normalizes.

Heres the log: View attachment 120421

Also, another problem I'm having is regarding Aquatic form, it seems that whenever my druid shapeshifts into aquatic form and moves for maybe 3 yards, the bot then makes it mount up in the water.
 
When the bot acquires a new target the following events happen:

1. Faces target and cat forms
2. Walk towards target
3. Begins combat

Here's the problem with #2, 80% of the time, my druid almost always tries to go behind the target (I can see the bot is clicking behind the target - directly opposite wherever the mob is facing) while also trying to move towards him in a bee-line fashion (similar to right-clicking a mob directly with click-to-move on). So basically it alternates between the direct and behind-the-target clicking every 0.1s, thus the stuttering, until he goes within melee range and everything normalizes.

Heres the log: View attachment 120421

Also, another problem I'm having is regarding Aquatic form, it seems that whenever my druid shapeshifts into aquatic form and moves for maybe 3 yards, the bot then makes it mount up in the water.

Thanks for the report. Will look at it later. :-)
 
New version.............:

Changed: Rewritten 3 Lua functions to non Lua to reduce Lag (3 are still missing.... :X)
Changed: Rewritten functions for energy checks
Changed: Calculations of Mangle, Rake and Rip damage now takes crit into account
Changed: Mangle damage calculations now take Feral Fury into account
Changed: We will now try to push buttons harder (200ms before HB recognizes that the GCD will expire.)
Fixed: A nullpointer exception
 
We will now try to push buttons harder

My keyboard just broke...

Other then that, looks awesome as always, looking forward to try the new version later tonight! :)
Thanks a lot for all the hard work and effort you put into this.



Sent from my GT-I9505 using TheBuddyForum mobile app
 
When the bot acquires a new target the following events happen:

1. Faces target and cat forms
2. Walk towards target
3. Begins combat

Here's the problem with #2, 80% of the time, my druid almost always tries to go behind the target (I can see the bot is clicking behind the target - directly opposite wherever the mob is facing) while also trying to move towards him in a bee-line fashion (similar to right-clicking a mob directly with click-to-move on). So basically it alternates between the direct and behind-the-target clicking every 0.1s, thus the stuttering, until he goes within melee range and everything normalizes.

Heres the log: View attachment 120421

Also, another problem I'm having is regarding Aquatic form, it seems that whenever my druid shapeshifts into aquatic form and moves for maybe 3 yards, the bot then makes it mount up in the water.

Hello again!

I've rewritten the movement logic. It now decides if it should move behind or not and only tries to do 1 of both behaviours.
I will upload the changes now.
Thanks again for your bug report.

Regarding Aquatic Form: I have so far no idea how to solve the problem. If it bugs to much you can disable Aquatic Form for now @ GUI.

Cheers
 
Uploaded a new version...

Changed movement
Improved rotation (On a 200m test i did 243k instead of 223k dps) :)
 
Running with Rune and TeD you often get insane RiP's and rakes. Sometimes the Routine seems to overwrite an insane Rip with a mediocre one, within the last 1 or 2 ticks of the strong one. From a min/max point of view its a dps increase to actually let the RiP run out and then reapply a weaker one.

Routine is strong as hell, it performs close to simc results, awesome work Handnavi!

e: will try the new one you just uploaded!

e2: yea that was a measureable DPS increase:)
 
Running with Rune and TeD you often get insane RiP's and rakes. Sometimes the Routine seems to overwrite an insane Rip with a mediocre one, within the last 1 or 2 ticks of the strong one. From a min/max point of view its a dps increase to actually let the RiP run out and then reapply a weaker one.

Routine is strong as hell, it performs close to simc results, awesome work Handnavi!

e: will try the new one you just uploaded!

Hey Apsalaar! :-)

The routine tries to take care of really strong rips and rakes.
Keep in mind that Rip is bugged. When you extend the dot it totally bugs out. If you extend it 3 times sometimes 3 ticks are added (and this is how it should work!).
But in general 5 ticks(!) are added to the current dot. The GUI sometimes even shows an extension of 6 or 7 ticks.
Very often Rip will suddenly fall off with >1-4 seconds remaining when 6 or 7 ticks were added.

Simc modelled the extensions to give 2-2-1 addiotional ticks. And so i did with Superbad. This helps to deal with the dot a little better.
 
Mad props for the fast replies and updates. Thumbs up for you brotha!
 
everyday i use this cr it seems to perform better and better. keep up the awesome work!
 
Status
Not open for further replies.
Back
Top