[PAID] [Warlock] Demonic - An Advanced Honorbuddy Warlock Routine [PvE/PvP]

Hey webhond!
Would u share ure settings with us? WOuld be awsm

 

May have found an issue - however the log files are a nightmare to read at the moment. I'm changing the logging in the next push to make it slightly easier to follow.

Manual cast detection will pause when you press an ability manually if that's what you mean?

Think I may have found a pausing issue, but yeah as above, logging isn't helping work out what's going on. There's nothing too obvious in the log (although the pausing is definitely there).

 

May have found the issue. Will test it later and push to SVN.

Nothing has changed with CB/Havoc for a while. You got a log ? It can miss them sometimes but most of the time should be fine.

Nothing obvious in there. Reduce your ticks per second down - 60 isn't necessary.. like 15-20 is fine.

 

I'll try to have a closer look at the whole situation next time, maybe i can explain a bit the whole situation with timestamps and behavior of the cr what it does, what it should do and so on, that makes it maybe a bit more clear for ya when reading your code
currently setting up a small CR for affliction only to support me while raiding

 

Thanks for fast replay.
Im running the game @ 160+ fps stable in arena, having the problem only in arena... in raid where i have ~90 fps i have no troubles.Aren't ticks per sec related to frames?
I have the problem since last HB patch and im using 60 ticks since i have option to.
Anyway ill try it and will post results soon.

 

Anyone else feel that it's kind of.. slow?
Running affli, I feel that it often waits to decide what it's going to do. When I say waits, I mean it doesnt do shit for like a second until it decides "oh yeah, that second dot!".
This is before the "pause fix" and after. Same stuff.
I'm used to the TuanHa responsive routines, while this really seems to be struggling to push all the abilities.

 

When doing what?

I've been testing it against target dummies, and it's pauses are very low (i.e. < 300ms between deciding whether to inhale/exhale or cast another spell).

 

Millz --

ChinaJade just replied to one of my posts about blacklisting evading mobs, and says it's the routine's job to blacklist (not Honorbuddy's). This is the post: http://www.thebuddyforum.com/honorb...back-honorbuddy-improvements.html#post1539840

So, what I'm posting about here is to ask if your routines have any sort of evade bug blacklisting code in them? Far too many times while running Quest bot have I seen HB get stuck on trying to kill a mob while it's evade bugged. It never gets blacklisted, and so it just continues to try and kill the mob. I'm one of those types that think's Blizzard is always trying to find the bots by sticking an evading mob into the game just to see who sits there and tries to kill it all day. So, if your routine doesn't blacklist, do you think that could be implemented? Some sort of anti-evade code or something that will blacklist a mob if it can't be killed in X seconds, then it moves on? Would be helpful and considered a safety feature.

 

I can't seem to get this to work in battlegrounds - I notice it says it doesn't support movement, does this mean I can't afk bot BGs with it? Because it does nothing in BGs, it won't target anyone until it gets attacked and then it starts fighting back but not very effectively.

 

I think you might have the Free Version of this Routine.
If you want to use the routine afkable you should run it with BG Buddy, and go to the settings in the routine and enable Movement + targeting and facing, auto focus and force combat etc, theres a default PvP profile you can load into it That works okay.
I have no problems in PvP with this routine, when i gets into problems is when they have healers and i dont

 

You say its slow?
Uhm how can I be pulling 1.2 mil damage per second on protectors HC?
Your settings must be playing with you, i had hard time setting it up also, but once you set it up its a beast!

 

Can some of you tell me your experience with battlegrounds in affliction and destro spec? Also is demonology supported?

 

I like to play both in PvP, battlegrounds so fun with Destro to 1 shots 2 people at once with havoc
Also in arena i do affliction becuase i like to support in there, and destro is more of an solo spec

But overall its good in PvP

 

Yeah, the routine has anti-evading logic built in. It adds a temporary blacklist when it detects the unit has evaded a spell.

 

this was before or after the pause change/fix?

 

I'm not sure the code is working then. There's been a few occasions where it's gotten stuck on an evade-bugged mob. The problem is that spells will hit (and damage) the mob, but then the mob will reset back to full health. I think this may be why it's not triggering the evade code in your routine. It's happened a few times while questing in Outlands, it's happened while grinding on Timeless Isle, it's also happened while questing in Eastern Kingdoms. Each time I've had to stop the bot, complete a quest, and move the bot along so it doesn't stick to the glitched mob. Have you seen this happen? Since it's been in the past that it's happened, I can't honestly give you a log for it because I'm not sure which of the 100s of logs it's in. When I get home today I'll begin looking through them to see if I can find it.

 

Hey - No you need to reload the bot, sorry.

Search the logs for either "Evading" or "Blacklist" and you should be able to find it. I'll need the log files though to be able to see what's happened.

 

well i tested affliction on dummy again, and it still does not what it should
still a lot of doin nothing,
- instead of casting MG it waits for something
- dots are completely fading from second target
- haunt is not refreshed how it should (takes much too long to refresh it)
and so on.
So pulling 1.2 mill dps is nearly impossible (at least with default settings) (not saying that it is impossible to pull 1.2 mill as affliction, i know this is not really a big deal in this fight at the correct itemlevel, but the routine is not able to come close to 700k dps atm)
So if u run it succesfully with that dps amount, i would be glad to test your settings
a screen of a castable (but not casted) haunt:
Screenshot by Lightshot

in my personal feeling the dotmanager does block the routine from performing how it should, maybe some stuff should be simplified a lot
currently i can pull more dps by playing the affliction lock on my own

and a corresponding log (removed the authorised as)

 

My Ilevel is quite high too tho.
I did 1.2m Yesterday late night, i didnt feel any dps change on the update tho.
Before the update i did about the same ending with 1.05 mil dps so they are quite close and its a bit RNG as you need everything to proc just fine.

You can pm me and i can send you my settings. Remember i also got Professions to maximize my dps as i proc it with my trinket procs etc.

Also the dps is not that high on dummy ofc. Also i do not use the drain soul as i would normally when the target hits 20%, theres no option to use the drain soul while its doing the normal rotation, if i allow the cancel for drain soul at % it will stop everything and spam drain soul and i wont have that

Edit: I tried the Default, and its casting Haunt. Its also casting haunt on the next target im focussing that should not happen, but overall its refreshing it haunt just fine

Try to reinstall HB and the combat routine.

Edit 2 : Your opener as Affliction is 1. Haunt 2. Dark Soul 3. Rotation.

What I do is i have a macro for Prepotting + Cast Haunt, and in the settings i have enabled Dark Soul on Cooldown and I'm Engineer and have allowed my Hand enchant use on Burst mode. So that means my macro Enable prepotting, cast Curse, Cast Haunt and then i let the rotation take over. Also note that the minimum HP allows the rotation to see which mobs to enable dots on etc. You should let it dot EVERYTHING Thats the way to get dps!

 

I found 2 bugs earlier today that I'll be pushing later. One *should* remove pausing, and another will fix the drain soul constant re-casting issue.