Screw PQRotation. No need to have another program running when HB can do it better (as you said).Well I can happily report that my FelHunter CC does about 1k more DPS than the latest hunter PQRotation on a dummy.![]()
Anyway to disable auto facing when using lazyraider? Otherwise great cc.
There are a bunch of cc's that you can raid with.... But honestly, none of them are that great. It's nigh impossible to create a DPS CC that can mirror or do better than a human being. There are too many variables, such as movement/distance/threat/general strategy among a multitude of other things which it makes it hard for the bot to compensate. Some type of rotation helper that is VERY limited would be great... something that you can turn on and off (or pause) as you please. However, this probably conflicts with HB since you can only turn it on or off and that locks my wow up 90% of the time lol.
get a lua hack protected hack > download ovale hacked edition (to use with lua hack) > download wow turbokeys > spam 1 for dps > more dps > profit
this is against the forum rules.
Hb does not do dps rotations better than pqr. Pqr takes as little resources that gb1 does and is only made for one single thing, processing rotations/monitoring buffs/debuffs.Screw PQRotation. No need to have another program running when HB can do it better (as you said).
And besides, PQRotation has no interaction with the area around you, where HB can look at a lot more than just your target and you.
Hb does not do dps rotations better than pqr. Pqr takes as little resources that gb1 does and is only made for one single thing, processing rotations/monitoring buffs/debuffs.
Now hb can do this well also but hb has a lot of bloat to make a good quick CC.
We have discussed this awhile back and we came to the agreement that for user controlled movement/facing in a raid environment and you want to maximize your dps go with pqr. If you want a tool that you flip on and is really good at arenas, bgs, automated processes like afk farming and leveling use hb.
There will always be specialized tools for specific tasks and if you ignore those other tools you are in a way shooting yourself in the foot.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
I don't think you know what you're talking about.
As I've had said in my previous post, one of the factors for a HB CC being not good is the fact the user's PC isn't strong. So, if your PC isn't strong, then you cannot possibly expect to run a CC so smoothly and effectively. This doesn't mean that HB doesn't do the rotations better than PQR. On a strong computer, It's about who codes better.
In fact, my PC is strong and the HB CC that I use far outperforms PQR. I have even tried out the PQR tool but some CCs from here are coded much better.
The point is that if a CC is well coded and even better coded than some PQR, then that CC will be the king, regardless of whether or not your PC is strong or not.
Your recommendation should change to "If you have a weak computer, use PQR, not HB. If you have a strong computer, use HB because it has better CCs "for the time being"."
I know I was debunking the whole hb must not work as well because the user is on a slow PC rant he was doing.If you read his post carefully imdasandman he doesn't say you have a weak pc.
I know I was debunking the whole hb must not work as well because the user is on a slow PC rant he was doing.
Sent from my SAMSUNG-SGH-I997 using Tapatalk
I think this will be a fabulous idea. I as well think it will add to the value of Honorbuddy.
However, I myself do not have the experience in coding CC's to do this. The most I can do is figure out errors from logs and edit profiles, Lol.
SO! What I can do to help is provide people the rotations/priorities need for every class and spec in order to create such CC's. I can as well test them out along with the community.
I hope some CC maker likes this idea enough to create one.
It will save me and the community lots of hours when we just don't feel like mashing buttons but, want that shiny loot ;D
Thanks,
xLegendx
Sorry for the wait Shad, I'll have a quick look @ my code while at work and toss it over to you from the iPhone.
It's very simple, but confusing at first.
One thing I have noticed is, at least on my pc, the time within the stopwatch was wrong.
Dealing with a few seconds should be fine, but when it got even into the minute I switched to DateTime and TimeSpans. Much more reliable.
They are normally used for longer times yes.Dont stress about it though, I may have found a solution with something that doesnt include timers at all! Although if that doesnt seem to work out, I wouldnt have to deal with anything above 30 seconds really!
So if WaitTimer works within a CC this would probably be the better option? Isnt DateTime normally used for time frames of 10+ minutes? For all i know i am mistaken... All these different timing codes really confuses me.