Its not how soul swapping works. Its a error in either the routine or in the bot, but i think its the routine.
It dots someone up, soul swaps to all in the neighbourhood and then uses MG on current / first target.
If it uses this at a full duration, nothing would be wrong, even if it is using it untill the dots need to be
refreshed, nothing was wrong, but it doesnt.
It goes like this : dot up, soul swap to all close , current target MG ( 0.1-0.5 sec ) - srop ( 1-2 sec ) - MG ( 0.1-0.5 sec ) stop ( 1-2 sec ) and then continues. This is VERY bot-like and deffo some bug.
I will try to switch to dx9 and see if that changes a thing. I doubt it, cause i have reported this issue over 6 months ago allready and then i was stil on dx9. And like i said, its not STOPPING completely, its just not functioning 100 % no more, sooner 60 % or less. It still works, but painfully. So its not the bot and it aint dx11 - dx9 or detaching itsellf from wow since its still workin, imo.
Looking at the posts the last day im not the only one, maybe try to find a sollution for it.
ty
If I want to turn on burning rush manually, do I need to stop the routine in order for it to allow my manual burning rush to be done quicker? Or will the routine pause for me pressing my hotkey for BR?
Hi Millz,
Affliction is still ... not good! (can't get more than 500k dps on 3 Targets, where i should have 750k and more)
There are still some pauses where no pausing should be needed, MG is not used enough (canceld much too early, not casted)
There are pauses with a timespan of 5 seconds and more without doin anything!
i'll list only the timestamps from the log where it starts the pausing
- 20:20:30.979
- 20:21:13.410
- 20:21:29.149 (i paused the routine after 3 seconds at this point, to interact with the toon by myself)
- 20:21:39.006
maybe u'll find something
->http://www.thebuddyforum.com/honorb...-warlock-routine-pve-pvp-553.html#post1537232
View attachment 131201
log 3 arena fights w balance druid
I repeat my question " Hi. The problem with the Havoc. Do not cast a double chaos bolt. In older versions, all was well."
In previous versions it was not working with the symbol is always now.
Few logs about my huge fps drops in arena since last HB patch
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).
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.
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.
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.
Can some of you tell me your experience with battlegrounds in affliction and destro spec? Also is demonology supported?
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.
this was before or after the pause change/fix?You say its slow?
Uhm how can I be pulling 1.2 mil damage per second on protectors HC?
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.Yeah, the routine has anti-evading logic built in. It adds a temporary blacklist when it detects the unit has evaded a spell.
I recently bought premium so I'm still kinda new at this, but there's one thing that is really nagging me. I play affliction PvP and Destruction PvE, and whenever I switch between the two I have to restart HB before it works, since stopping the bot and changing class profile under "Settings & Tools" doesn't work. Is there any way to not have to restart the bot before it works?
Oh and your routine is fantastic!![]()
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.
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)
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)