Well I can happily report that my FelHunter CC does about 1k more DPS than the latest hunter PQRotation on a dummy.
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.
Your processor calculations ARE much faster than your own brain. So, when you run a CC in real time, your processor will process the CC and then initialise actions based on certain checks almost instantly. However, all of that depends on how well the CC is coded and how strong your processor is. If a CC is well coded, uses checks (use #A skill 0.500 msec after when you get a proc, or whatever), auto-interrupts and do the rotations in a timely and proper fashion (skill->0.5 sec->skill 2->0.5 sec->skill 3, etc.) then that CC should be able to output better DPS/work than "most" players - assumed that you have a good processor too. This concept is just the same as healing CC(s). On the other hand, hand players may delay thier rotations because they are too busy moving or getting distracted by vent, or human mistakes (people sometimes forgot what skill to use next). There are some CCs that are badly coded and there are also bugs... that all make the rotations, checks, actions, etc. slower. But my point is that it's very possible to deal the highest DPS with a CC (proved by some excellent CCS here)...
Like Amplify, for just Frost anyways. I always forget about coldsnap and when my elementals freeze comes off CD. I'll see what I can do in about a week for updating/adding to CCs that I use anyways And in about a month+1 week I'll have much more time for coding... Time to get my Buddy(plugins) up to the point they were intended.
some classes need really updates in CC for lazyraider and for questing. is fps still alive? or some other? look like some classes are getting dead (Hunter, RetPala ...)
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"."
Lawl your cute.. I do not have a weak PC. Yes some CC are better on hb some profiles are better on pqr. My PC isn't weak at all I can run 4 wow sessions 3 of which will be hb and run my main account with pqr at 1920x1080 while doing live logging with the WoL tool and fraps and play music all on the same comp and still get 40fps on high settings in a 25man raid Each tool has its advantages and disadvantages. Don't be a damn fan boi Sent from my SAMSUNG-SGH-I997 using Tapatalk
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
Which is correct, depending on the CC Huge CCs that has to process alot of information will work better on a good computer, than a weaker one. Also, there are already quite a few raiding CCs out there. What class are you having trouble with finding a raiding CC for? I haven't done a single raid p? hand in a long long time and i have yet to see a time i haven't been in top 3 in 25 mans.
Im basing all my Lazyraider CC's on raid rotations(Everything is based on Elitist Jerks theory crafts). I keep them simple so they dont have to process much information which makes them quick. However as im very new to coding i have my share of problems. An example is if Me.CurrentTarget.HasAura("Living Bomb") == false (CastSpell("Living Bomb") == true. This doesnt work in raids 90% of the time, because theres another mage there casting Living Bomb. So this is my main issue, to have a code that solves that issue. Ive tried making Stopwatch to keep track of this, however it doesnt work properly. So i wonder if theres another function for this? Perhaps WaitTimer?
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.
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.
They are normally used for longer times yes. You should be able to do something like this tho: Var tarAuras = Me.CurrentTarget.Auras; Foreach (WoWAura aura in tarAuras) { If(aura.Name == "SpellYouWant" && aura.SomethingAboutCastedByCharacter) Blahblah } There is a way to check what unit caused the aura to be on the other unit. Maybe have a look at the healing CCs since they should have a way to deal with it.
