What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

[PAID] [Priest] Insanity - An Advanced Honorbuddy Shadow Priest Routine [PvE/PvP]

Hey Millz, do you have any recommended settings for AS - shadow build? I have about 694 ilvl and can only pull about 20-25k deeps on gruul when normally I can get 40-45k myself. Idk what it's doing wrong but if you have any advice for me that'd be great!

also, is there any way to keep dots up on all mobs near me? doesnt seem to be dotting anything during aoe
 
lolspeedo said:
Hey Millz, do you have any recommended settings for AS - shadow build? I have about 694 ilvl and can only pull about 20-25k deeps on gruul when normally I can get 40-45k myself. Idk what it's doing wrong but if you have any advice for me that'd be great!

also, is there any way to keep dots up on all mobs near me? doesnt seem to be dotting anything during aoe
Click to expand...
Have youu tried cop.....i dont raid o spriest. But the research i did back a while ago i thought i remember cop being better single target but i could be totally wrong......just a sugestion.
 
Quick heads up on the new builds upcoming changes. Haven't pushed it public yet.

- Logging now shows last 4 characters of target GUID to help determine difference between multiple units.
- Overlay will now keep the same position between HB restarts.
- Fixed an issue that could cause problems with saving settings due to new store security.
- Hotkeys/Overlay settings are now stored separately to the normal routine setup. This means when loading new setting files, the hotkey config won't change. *NOTE* This does require hotkeys to be re-configured for the first time after this update.
 
Millz said:
Quick heads up on the new builds upcoming changes. Haven't pushed it public yet.

- Logging now shows last 4 characters of target GUID to help determine difference between multiple units.
- Overlay will now keep the same position between HB restarts.
- Fixed an issue that could cause problems with saving settings due to new store security.
- Hotkeys/Overlay settings are now stored separately to the normal routine setup. This means when loading new setting files, the hotkey config won't change. *NOTE* This does require hotkeys to be re-configured for the first time after this update.
Click to expand...


Hi millz, getting massive lag on your routine, Tried with both raid and enyo botbases, fiddling with frame locks, nothing worked. Log included:
 

Attachments

Spank said:
Hi millz, getting massive lag on your routine, Tried with both raid and enyo botbases, fiddling with frame locks, nothing worked. Log included:
Click to expand...

Hey

Can you try the following (1 step at a time until you find the issue!);

- Enable Anti-Lag #1 and #2 in the advanced tab
- With Enyo, reduce the TPS to 10.
- Disable the sounds / overlay on the advanced tab

Let me know how you get on!

Cheers
 
Millz said:
Hey

Can you try the following (1 step at a time until you find the issue!);

- Enable Anti-Lag #1 and #2 in the advanced tab
- With Enyo, reduce the TPS to 10.
- Disable the sounds / overlay on the advanced tab

Let me know how you get on!

Cheers
Click to expand...

Dropping the ticks to 10 per second seems to have stablised it, even with anti lag 1 and 2 up, it still spiked in frame rate.

So it seems to be running okish atm. Will update once I raid on wednesday
 
Spank said:
Dropping the ticks to 10 per second seems to have stablised it, even with anti lag 1 and 2 up, it still spiked in frame rate.

So it seems to be running okish atm. Will update once I raid on wednesday
Click to expand...

Cool, at least that's a bit better. There's a few reports of FPS issues since the latest HB update - more likely related to a wider problem.
 
trashmaster said:
Hello Millz

Could u please have a look in the log? I enabled AoE, its 3 by default but I never see the CR using mind sear when I quest or when Im in dungeon and tank pulls large number of mobs.

View attachment 180467


thx
trashmaster
Click to expand...

I hadn't updated the code after the level you get Mind Sear reduced from 76 to 28.

I'll push a new build with the fix in :)

Cheers
 
Routines working great so far for leveling. 90-96 without any issues. Glad to see your still keeping all of your products updated. Looks like the banwave took out the DK guys (at least for the time being). So you'll have a new customer once my trial is up!
 
Montero said:
Routines working great so far for leveling. 90-96 without any issues. Glad to see your still keeping all of your products updated. Looks like the banwave took out the DK guys (at least for the time being). So you'll have a new customer once my trial is up!
Click to expand...

Cool! Glad you're enjoying it.
 
M8 I love the rotation a lot. Just wondering how and if it tracks the Auspicious Spirits. Seems im overcapping a lot since it seems to favor putting up SW:P over getting rid of DP. Especially with 4 orbs and 3 AS underway to the boss.
 
ull4givme said:
M8 I love the rotation a lot. Just wondering how and if it tracks the Auspicious Spirits. Seems im overcapping a lot since it seems to favor putting up SW:P over getting rid of DP. Especially with 4 orbs and 3 AS underway to the boss.
Click to expand...

DP is top priority when you're going to cap. It doesn't track the AS spirits moving to targets (that would require an immense amount of scanning for targets), but it can roughly predict what's going to happen.

It'll use DP on target where possible, but dump on off-targets when capped if current target has DP active still.

If you're @ 5 orbs and standing spam casting SW:P then that's a big issue - if that's what you're seeing then can you post a full, unedited log file please?

Ref: How To Attach a Log
 
Millz said:
DP is top priority when you're going to cap. It doesn't track the AS spirits moving to targets (that would require an immense amount of scanning for targets), but it can roughly predict what's going to happen.

It'll use DP on target where possible, but dump on off-targets when capped if current target has DP active still.

If you're @ 5 orbs and standing spam casting SW:P then that's a big issue - if that's what you're seeing then can you post a full, unedited log file please?

Ref: How To Attach a Log
Click to expand...

Thanks for the quick respons.

It seems to find SW:P dot more important and I find myself capping to much. With AS you should ditch it as soon as you have 3. Or you will cap so quick when there are like 5-7 Spirits underway. And it sucks to see it at 5 orbs with like 7 Spirits underway and it not using DP.

Also when If I say VT on 1 target ( which is just better especially in multidot fights) it just puts it up twice or even three times every now and again.

Does it read like health etc as well? I see it try to dot loads of low health mobs over using Cascade for example. Which makes perfect sense in some situation, but Cascade or Halo shouldnt be on cd for more then 10 secs. Especially on 4-5+ adds.

I see it uses MS/SI with loads of mobs which makes sense. But when mobs die fast, like at Beastlord Darnac HC, they wont live long enough for even 2 ticks of SW:P. So better to just shoot a Halo/Cascade in there to max deeps and then after MS/SI. Seeing it trying to DOT them up is a waste:)

I'm doing Blackhand tonight so not the best example boss, but will do like a LFR later or tomorrow and I will give you a log.

EDIT: Did some dungeons this morning and in both UBRS and IRON docks it overcapped from the start:) Hope this helps! Need anything else just ask.
 

Attachments

Last edited:
ull4givme said:
Thanks for the quick respons.

It seems to find SW:P dot more important and I find myself capping to much. With AS you should ditch it as soon as you have 3. Or you will cap so quick when there are like 5-7 Spirits underway. And it sucks to see it at 5 orbs with like 7 Spirits underway and it not using DP.

Also when If I say VT on 1 target ( which is just better especially in multidot fights) it just puts it up twice or even three times every now and again.

Does it read like health etc as well? I see it try to dot loads of low health mobs over using Cascade for example. Which makes perfect sense in some situation, but Cascade or Halo shouldnt be on cd for more then 10 secs. Especially on 4-5+ adds.

I see it uses MS/SI with loads of mobs which makes sense. But when mobs die fast, like at Beastlord Darnac HC, they wont live long enough for even 2 ticks of SW:P. So better to just shoot a Halo/Cascade in there to max deeps and then after MS/SI. Seeing it trying to DOT them up is a waste:)

I'm doing Blackhand tonight so not the best example boss, but will do like a LFR later or tomorrow and I will give you a log.

EDIT: Did some dungeons this morning and in both UBRS and IRON docks it overcapped from the start:) Hope this helps! Need anything else just ask.
Click to expand...

Thanks for the log/write up. There's a couple of points in there where it caps when it shouldn't. I've made a couple of changes to help with this (not pushed to store yet, need to test).

It doesn't check HP values explicitly, but rather how long it estimates the unit will have left until it will die (time to die - TTD). For SWP, it won't refresh if the target has less than 12s to live, and VT is 10s. It takes ~2 seconds from units (or us..) entering combat for the bot to calculate a rough TTD value. It takes ~5 seconds for the value to be accurate.
 
Millz said:
Thanks for the log/write up. There's a couple of points in there where it caps when it shouldn't. I've made a couple of changes to help with this (not pushed to store yet, need to test).

It doesn't check HP values explicitly, but rather how long it estimates the unit will have left until it will die (time to die - TTD). For SWP, it won't refresh if the target has less than 12s to live, and VT is 10s. It takes ~2 seconds from units (or us..) entering combat for the bot to calculate a rough TTD value. It takes ~5 seconds for the value to be accurate.
Click to expand...

Awesome that you might have found a solution. When our crit levels will rise to even higher levels in the next tier it will be more of a problem. After some more testing it's when AS spawn to much it seem not to register the incoming orbs or something.

How about the stubborness of VT that is sometimes still being applied? That me doing something wrong in settings or just random hickups?

TTD makes sense... since adds at for example Darmac in our raids hardly live 2-3 seconds. So no wonder it doesn't register it and dot's it up.

P.S. IF you need an extra tester I'm all yours!
 
You must log in or register to reply here.
Back
Top