CLU (Codified Likeness Utility)

Sure about that guys?

 

Wulf,
Just tested this out on my Destro Lock. It seems to do the rotation well but, your felmaster rotation on it is smoother. It does not prioritize conflagrate, or when you have empowered imp properly. Also, just from running a few instances with it if you are moving it will not say switch over to fel flames. Sorry i have not posted a log as there was no real bugs. With a 388 ilevel pulling about 18k with CLU same i level same fight duration with felmaster and your rotation pulling 20.3k. i will test out more of the classes soon. Keep up the good work.


Actually after giving it a few more runs on the test dummy it will go into a soul fire spam chain and cast it about 3-4 times. I will attatch a log after it finishes a good timeframe of rotation.

 

Thanks everyone, it seems I have some work ahead of me!

I will change Ravage! //Thanks handnavi, laria

bennyquest, thank you for taking the time to test and provide feedback. I too get the same results and will be looking into resolving the issue.

All of these issues are fixable, it will just take time. I will only concentrate on the classes currently available to make them as perfect as possible then move onto the others!

 

no problem, if there are any of the other classes that are not tested i will gladly test rotations out and let you know how off the rotation is. I just am not that great with the coding aspect of it.

 

I was just doing Ultraxion and using the masterfrost DK. An ally died and the bot started to spamtarget the ally without ressing. Its at the end of the log

 

Your masterfrost might actually be doing more then PQRs. Good work.

 

Sorry I deleted my last post but logs have toons name in it (I think) ...
GOOD NEWS: no longer lag spikes YAY

New problem:
Honorbuddy version: Latest!
Class: DeathKnight (masterfrost)
Level: 85
Group: Raid
My Latency is: 60ms
My Computer is: Modern
Made any changes: No
Issue/Bug/Problem/Suggestion: If the max number of battle rezes have been used the dk will keep trying to rez ... ultimately stopping you from dpsing


Log: I cant seem to find the log where it was doing this ... I will try to recreate this situation


My idea of a fix: instead of auto raising ally have the dk only cast raise ally on who have you set focus too ...

again sorry about the log

 

Personally, it's a cool idea to have it auto-rez but no true raid is going to want you to be auto-rezzing on ultraxion and such, wasting it on a dps instead of a tank/healer could get ya yelled at by your leader.

 

I think you misunderstood the issue ... let me re-explain:

The auto rez funtion of the DK IS WORKING, however (lets say in a 10m raid) one person dies and gets battle rezed then another person dies this CC will try to rez the second dead person. This cannot happen becasue in a 10m raid the group is only allowed 1 battle rez.

I know very little about coding but my suggestion to fix this issue would to instead of having the CC auto rez (like it does in its current state), have the CC rez who your focus is set to ... like with rogue CC's they trix their focused target.

So the scenario would look like this:
Someone dies -> You manually right click their name in the blizzard ui and set then to your focus -> CC then rezes

 

I get that, I'm just saying the feature isn't practical in a serious raid at all. Manually focusing them would take more time then just clicking on them and using the spell yourself.

 

yes, sorry the auto rez functionality bug existed in felmaster i forgot to disable it again. I will disable when I get off work and until I code theFindTankorHealer(WoWunit unit) method. This will allow it to only rez a tank or healer (whichever dies first in this order, Tank, Healer). It will not attempt to reuse the battle rez if one has already been used.

Thanks for your feedback guys, appreciate it.

 

So just tested your latest improvements and there are definitive improvements!
But it still gives micro freezes. The time a frame was frozen has been reduced to some ms but the time between those freezes is lowered too, like every half second it freezes for some ms and continues.
I tested it with the RaidBot and my private Singular edit is easily outdpsing yours. Yours got to 26k DPS constant DPS after 5min and my Singular edit runs 30k straight for 5min.
So there is still room for improvements and I would suggest to make an option for logging, because its only necessary for debugging purposes.
And maybe you should get rid of that rune timers. I don't use them and still everything is fine. But that's more an quality of life issue.

And I pm'd you because I need an unused eye to look over some code which I don't get to work.

greetz

Weichbier

Edit: Man, your ionbox is full ... get rid of those FanToys

 

Haha inbox is empty

Thanks for testing again! currently removing and consolidating all of the code.
There is allot of obsolete and redundant code. (And code that can be optimized)

Logging will be disabled ASAP (with the ability to toggle on and off.) I needs to seeee!

Coding is like a drug lol....I cant read enough!

 

Would this work for the alysrazar encounter in firelands where you can cast while moving with the special buff?

 

Going to have to have a week or so off from this project, I am in the middle of changing jobs and everything is up in the air. As soon as things settle down I will be back with some nice improvements/fixes!

 

Back.

Change Log
-------------
* 24/2/2012 [2.0.4] RIADBOT now usable, CanCast bug fixes, Debug logging off by default, general code standardisation changes

 

Would you consider shaddars ultraxion and madness helper and maybe znfs raidwarning for positioning behind the boss for even more awesomeness?

 

Change Log
-------------
* 24/2/2012 [2.0.5] RIADBOT tweaked to not spam like a mofo, Fixed warlock spamming Soul Fire, Fixed Paladin consecration, general code standardisation changes

 

If shaddars and znfs are willing to give me permission to implement this, maybe. Otherwise no, as its their great concepts/ideas.

 

Thank you for you job but... emm... another one AllInOne CC? Can you explain why did you start new project instead working on Singular? Will your projct better?

P.S. Sorry I wouldn't blame you. This is only questions.