What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[WIP] Singular - A community driven All-In-One CC - It Just Plain Works

Status
Not open for further replies.
Heres a hunter patch that adds call pet & should add revive pet too but i cant confirm this as my pet hasn't died despite me trying

Edit: does rev the pet

Edit 2: could you add some kind of code for me so that it checks lua for a pet is dead when casting call pet; thats a bit too advanced for me
 

Attachments

Last edited:
Update to the fury portion.

Latest Additions:
- Uses most Racials.
- Will no longer spam hamstring on targets with slowing poison.
- Uses Recklessness
- Uses Engineering gloves
- Casts lifeblood

Bugs:
- Sometimes when casting Death Wish the bot will stop moving to mele range.

/brag The bot did 13.5k Dps single target sustained damage on a heroic dummy
 

Attachments

Updated the first post.

Added Jon310's fury war changes. (Sorry, I can't test, so lets hope they work) - I had to modify them slightly due to API changes. Also removed some redundancies. (Please check the changes, and let me know if I mucked something up.)
 
Getting this as of 144

Could not compile CC from C:\Users\Neix\Desktop\Honorbuddy\CustomClasses\Singular!
File: Line: 0 Error: Unrecognized option: '/optimise'
 
Nuok said:
Getting this as of 144

Could not compile CC from C:\Users\Neix\Desktop\Honorbuddy\CustomClasses\Singular!
File: Line: 0 Error: Unrecognized option: '/optimise'
Click to expand...

Ditto for me...
 
Odd, just remove the //!CompilerOption:Optimise:On in SingularRoutine.cs.

I'll figure out whats wrong with that in a minute. (Might be a bad compiler version on your end)
 
Nuok said:
Getting this as of 144

Could not compile CC from C:\Users\Neix\Desktop\Honorbuddy\CustomClasses\Singular!
File: Line: 0 Error: Unrecognized option: '/optimise'
Click to expand...

Just as a heads up i have reversed r138 in SingularRoutine.cs and removed compiler options for now and it is working again for me atleast.
 
Are there PvP-Rotations + Logic fully implemented in the DK-Part? My Frost DK needs some HonorPoints :)
 
Apoc said:
Odd, just remove the //!CompilerOption:Optimise:On in SingularRoutine.cs.

I'll figure out whats wrong with that in a minute. (Might be a bad compiler version on your end)
Click to expand...

Maybe, heres a log if it helps
 

Attachments

Also as a note, it seems like there is no check to make sure the target is infront of the character for fury warriors. Fixed on my local version but thought i would let yall know (well also do other extensive testing/feedback/optimizing for fury warriors).
 
Apoc, thanks for adding my work to singular.

I'm testing the changes and found an issue with facing targets once in combat. I had the same issue before, and solved it with a CreateLosAndFace right after the ensuretarget in the combat section.

Also, My char just ran away from a mob spamming intercept. He was not facing the mob so he could not cast the spell. Another CreateLosAndFace might not hurt in the beginning of the pull section as well.

When pulling with heroic throw, the toon will run to the place the mob used to be. This would most likely be fixed with the changes listed above.

Thanks, Jon

Edit: I see CreateLosAndFace was removed. Thats a shame, it really helped sort out mele bugs in this cc. Any way to get that back in?
 
Last edited:
My ret paladin doesn't like to chase after runners. :(
Sometimes it doesn't even run to the mob.
 
The CreateLosAndFace func did nothing more than the new CreateMoveToAndFace (just pass it the unit to get LOS with)

I renamed them to remove the confusion about what they do. (They were literally the same)
 
Maybe the issue is that CreateMoveToAndFace(ret => Me.CurrentTarget) is at the bottom of the priority tree after all the spells; try moving it up to the top. If you wanted to have it do stuff at range and mele maybe try having two of them so

--CreateMoveToAndFace(30f, ret => Me.CurrentTarget),
--Ranged spells,
--CreateMoveToAndFace(5f, ret => Me.CurrentTarget),
--Melee stuff
 
It was less for the Los and more for the face part of it. I put it at the beginning of the priority list just to ensure that the char was facing the mob/player before any spells were cast.

Without a face check at the beginning of the priority list the bot will frequently stand with mobs at its back spamming its next mele skill facing nothing. If there is some other way to acomplish this let me know, I'm not very good at coding.

Thanks, Jon

@Nuok, Thats similar to what I did to resolve it before.

Edit: Im having no issues with a CreateMoveToAndFace(ret => Me.CurrentTarget), added after ensuretarget in the combat section.
 
Last edited:
Added the lines to both Pull and Combat. Should resolve the issues for Fury.
 
Shadow

Heres a patch for the Shadow Priest rotation.

Due to the nature of shadow, with instant cast DoTs, I added a few checks for IsMoving and also some mana checks to both Archangel and Shadowfiend.

As it stands, you could probably use this in a raid, since it will allow you to move and not break the sequence (i.e. it will use DoTs, but not try to Mind Flay/Mind Blast/Vampiric Touch). If you're just using it standing still, you wont notice a difference except for the timing on Shadowfiend/Archangel. This just adds an extra element of checking to it for people who like to use Mr. Autofight in raids and stuff.
 

Attachments

this thing kicks arse i wish it would detect pvp an hamstring an shattering throw
 
Thought i would contribute to the lovely CC. I am relatively new to HB development so im still trying to find my way around. I went ahead an optimized the the changes that Apoc/Jon310 made to fury warriors.

Note: Alot of these changes could also apply to Arms warriors aswell
Changes:
-Better utilization of Recklessness
Will be used only when deathwish is active,
Won't be used if you are below 15% health to avoid wasting the CD​
-Deathwish is better utilized to only be used in certain situations. Will be used when:
-Boss *like* Situations
Has more max health than you​
Target is below 95% health before using (so not to pull agro)​
Have 50+ rage so you can dump some damage​
Emergency/PVP *like* Situations
You are not below 10% health as to not waste CD​
Target has more health than you and you are below 60%​
-Added support for Incite (obviously if you are spec'd for it) HS will be used if Incite has "proc'd
-Added Inner Rage. Will be used when any of the following occur:
Recklessness, Deathwish, or you have greater than 80 Rage to help with rage dump​

I also had change my local version to support Fury of Angerforge (since alot of warriors have it, including me). I wasn't sure if you would want something like that so it took it out, but can add it if you would like. Fury of Angerforge - Item - World of Warcraft

I saw just under a 10% increase in damage from revision 151 to the modified version (that includes not using cooldowns like it was doing before!)

Still need to do more testing/optimizing but those things were bugging me the most :). Apoc/Raphus/ anyone else feel free to edit/revise my changes as needed since i'm a little new to HB development
 

Attachments

Last edited:
Status
Not open for further replies.
Back
Top