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

Singular - A community driven All-In-One CC - It Just Plain Works - (Pt. 2)

Apoc said:
CooldownTimeLeft.TotalSeconds < 6 should resolve the CS problem.

As for Shattering Throw, you need to make sure you stop movement.

Code: 
                new Decorator(ret=>StyxWoW.Me.CurrentTarget.HasAnyAura("Hand of Protection", "Divine Shield", "Ice Block"),
                    new PrioritySelector(
                        Spell.WaitForCast(),
                        Movement.CreateEnsureMovementStoppedBehavior(),
                        Spell.Cast("Shattering Throw"))),

Somewhere before your other stuff should work. (If not, lemme know. I'd suggest putting it before any other movement code to ensure you sit still while you cast it)
Click to expand...

Nice, thanks Apoc!
 
hi guys!

did something change for Prot?
when i disable the movement,i still have problem to select the add,the bot,don't allow to me to do that(it's like automatic select)...it's kind hard when i fight the boss in Blackrock Cavern(CORAL boss).....
any idea pls?

thanks!
 
yipsilonn said:
hi guys!

did something change for Prot?
when i disable the movement,i still have problem to select the add,the bot,don't allow to me to do that(it's like automatic select)...it's kind hard when i fight the boss in Blackrock Cavern(CORAL boss).....
any idea pls?

thanks!
Click to expand...

I've noticed this too with Arms a few time when doing arena's. With movement disabled it, sometimes when I try to switch targets, it won't do it, it keeps re-selecting the one I was targeting.
 
I added a setting to the Paladins that you can set to not auto-change auras. This is good for gathering so that you can fly around with Crusader on and not have it switch every time you land to gather a node. Not sure if this interests anyone else using this or the devs to commit to the SVN.
 
Apoc said:
CooldownTimeLeft.TotalSeconds < 6 should resolve the CS problem.

As for Shattering Throw, you need to make sure you stop movement.

Code: 
                new Decorator(ret=>StyxWoW.Me.CurrentTarget.HasAnyAura("Hand of Protection", "Divine Shield", "Ice Block"),
                    new PrioritySelector(
                        Spell.WaitForCast(),
                        Movement.CreateEnsureMovementStoppedBehavior(),
                        Spell.Cast("Shattering Throw"))),

Somewhere before your other stuff should work. (If not, lemme know. I'd suggest putting it before any other movement code to ensure you sit still while you cast it)
Click to expand...

I'm still having issues getting the CooldownTimeLeft.TotalSeconds implemented. Everything I try is giving me errors.


EDIT: Other than that everything for fury has been implemented.

- Inner rage for AOE
- DPS coolddown option only stops Recklessness and Death Wish
- Commanding shout / Battleshout option in the cc
- T12 use of commanding or battleshout off cooldown option
- Rather than auto detection for SMF or TG I just added the option in the GUI.
- BasicDPS rotation turns off all the frills, no intercept, no slows, no cooldowns, nothing but the basic rotation.


Now I'm off to fix arms, get it up to par with fury.

Edit 2:

Arms is on par with fury now as far as options go.
Fixed Shattering throw.
Added an option to not use slam if not talented (PvP)

Added shattering throw to fury pvp
Fixed Heroic leap, it works again.

I destroyed my buddy(paladin) with both specs duel testing the features and options of both specs. Thing is a beast.
 
Last edited:
Jon310 said:
I'm still having issues getting the CooldownTimeLeft.TotalSeconds implemented. Everything I try is giving me errors.


EDIT: Other than that everything for fury has been implemented.

- Inner rage for AOE
- DPS coolddown option only stops Recklessness and Death Wish
- Commanding shout / Battleshout option in the cc
- T12 use of commanding or battleshout off cooldown option
- Rather than auto detection for SMF or TG I just added the option in the GUI.
- BasicDPS rotation turns off all the frills, no intercept, no slows, no cooldowns, nothing but the basic rotation.


Now I'm off to fix arms, get it up to par with fury.

Edit 2:

Arms is on par with fury now as far as options go.
Fixed Shattering throw.
Added an option to not use slam if not talented (PvP)

Added shattering throw to fury pvp
Fixed Heroic leap, it works again.

I destroyed my buddy(paladin) with both specs duel testing the features and options of both specs. Thing is a beast.
Click to expand...

Awesome thanks!
Did you make a way so that with fury it will use Berserker Rage on CD somehow?

Also, is there a way to have it JUST do the basic rotation, but still have an option for hamstring?

Thanks! +Rep
 
Apoc there seems to be an issue with tanktargetting in dungeons. I'm tanking as DK Blood in Azjol-Nerub, and pretty much from the beginning the tank wants to select a target that's no where near me, in this case Hadronox. I experienced the same issue in The Nexus where the bot would target a flying dragon instead of the pack I was actually fighting.. makes it hard to keep aggro until you clear/move past that area with a "bugged" target..

I hope you understand what I mean - not sure a log file would make it clearer..

Regards
 
loevstroem said:
Apoc there seems to be an issue with tanktargetting in dungeons. I'm tanking as DK Blood in Azjol-Nerub, and pretty much from the beginning the tank wants to select a target that's no where near me, in this case Hadronox. I experienced the same issue in The Nexus where the bot would target a flying dragon instead of the pack I was actually fighting.. makes it hard to keep aggro until you clear/move past that area with a "bugged" target..

I hope you understand what I mean - not sure a log file would make it clearer..

Regards
Click to expand...

Something is def. up with Singular's targeting. It's like disabling movement doesn't entirely disable the targeting feature all the time.

Also, Apoc, are we anywhere close to having that bug fix for large boss target hit boxes update?

Thanks!
 
Jon310 said:
I'm still having issues getting the CooldownTimeLeft.TotalSeconds implemented. Everything I try is giving me errors.


EDIT: Other than that everything for fury has been implemented.

- Inner rage for AOE
- DPS coolddown option only stops Recklessness and Death Wish
- Commanding shout / Battleshout option in the cc
- T12 use of commanding or battleshout off cooldown option
- Rather than auto detection for SMF or TG I just added the option in the GUI.
- BasicDPS rotation turns off all the frills, no intercept, no slows, no cooldowns, nothing but the basic rotation.


Now I'm off to fix arms, get it up to par with fury.

Edit 2:

Arms is on par with fury now as far as options go.
Fixed Shattering throw.
Added an option to not use slam if not talented (PvP)

Added shattering throw to fury pvp
Fixed Heroic leap, it works again.

I destroyed my buddy(paladin) with both specs duel testing the features and options of both specs. Thing is a beast.
Click to expand...

Jon, how is the rotation for Prot looking? Is it possible to enable/disable it's CD's, do basic rotation, ae support, rend+thunderclap, etc.?

Thanks!

Edit: noticed that fury spec isn't changing back to berserker stance for rotation.
Should think about a fix, but then also basic rotation should disable all stance swapping - except for going to Battle to rip off bubbles.

Thanks!
 
Last edited:
Zacharybinx34 said:
Awesome thanks!
Did you make a way so that with fury it will use Berserker Rage on CD somehow?

Also, is there a way to have it JUST do the basic rotation, but still have an option for hamstring?

Thanks! +Rep
Click to expand...

I will not be making it use berserker rage on cooldown. As it is now it will pop it if you are not enraged so as to keep an enrage up as much as possible. Keeping dps in mind it is not advisable to pop it off cooldown.

I can put slows back on the basic rotation list.


Zacharybinx34 said:
Jon, how is the rotation for Prot looking? Is it possible to enable/disable it's CD's, do basic rotation, ae support, rend+thunderclap, etc.?

Thanks!

Edit: noticed that fury spec isn't changing back to berserker stance for rotation.
Should think about a fix, but then also basic rotation should disable all stance swapping - except for going to Battle to rip off bubbles.

Thanks!
Click to expand...

I haven't taken a look at the prot tree, that one was written by someone else. I don't use instancebuddy or tank dungeons, so I have no real way to test the changes.

I can take a look and modify things if its cool with Apoc and raphus, but any of the more advanced things (like targeting) I really cant do.

I haven't noticed the warrior staying in battle stance when shattering throwing. Ill see if I can add a stance check so that it keeps proper stance.
 
Movement isn't targeting.

If you're using tank targeting, I highly suggest you leave it alone. (I may add an option to allow you to deal with targeting yourself, though I suggest leaving it as-is unless you're raid tanking.) It will automatically switch to targets its losing threat on. (It should only be including targets actually in combat with the party, so I'll have to get more info on the issue reported by loevstroem.

@Jon310; I wrote the Instance version of prot. Feel free to implement PVP/World versions. (Check the Context attrib on the func)

Edit; just added tank target disabling. Not tested, so lemme know if it works
 
Last edited:
Apoc said:
Movement isn't targeting.

If you're using tank targeting, I highly suggest you leave it alone. (I may add an option to allow you to deal with targeting yourself, though I suggest leaving it as-is unless you're raid tanking.) It will automatically switch to targets its losing threat on. (It should only be including targets actually in combat with the party, so I'll have to get more info on the issue reported by loevstroem.

@Jon310; I wrote the Instance version of prot. Feel free to implement PVP/World versions. (Check the Context attrib on the func)
Click to expand...

While you're here can you give me an example of how the CooldownTimeLeft should be implemented? I still cant get that working, and everything I try shows errors.
 
Jon310 said:
I will not be making it use berserker rage on cooldown. As it is now it will pop it if you are not enraged so as to keep an enrage up as much as possible. Keeping dps in mind it is not advisable to pop it off cooldown.

I can put slows back on the basic rotation list.




I haven't taken a look at the prot tree, that one was written by someone else. I don't use instancebuddy or tank dungeons, so I have no real way to test the changes.

I can take a look and modify things if its cool with Apoc and raphus, but any of the more advanced things (like targeting) I really cant do.

I haven't noticed the warrior staying in battle stance when shattering throwing. Ill see if I can add a stance check so that it keeps proper stance.
Click to expand...

Hey John.
Slows being on the rotation list is fine so long as their is an option to disable slows - which I think there is.

I'm pretty sure that with berserker rage being glyphed you want to pop it on CD, I could be wrong, but I'm fairly certain it's more dps overall to pop it on CD. Have you reseached this?

Tanking only needs options to disable/enable cooldowns - with AE support including shockwave and rend + Thunderclap options. From what it seems apoc has implemented a disable target option.

Apoc, is that also usable for arms/fury? I notice it sometimes will keep targeting my target in arena's when I am trying to change targets.

Jon. Did you look to see if there is anyway to ensure the cc will never do Improved Slam and Raging Blow back to back? We need to ensure every other attack is bloodthirst.

Thanks!
 
HEY Apoc !

Bobby has implemented an awesome feature in his ShamWOW Custom Class - the ability to start the next cast RIGHT before the current cast finishes - its called [Account for Lag]

Would it be possible to make Singular default do this for every class? That would DRAMATICALLY speed up dps rotations. Of course, it should probably be an advanced option to check - since the user would have to turn this on in game as well by checking Wow's Lag 'Lag Tolerance' option under [Combat] in [interface options]

I think this would be amazing! My fury warrior's rotation would be near perfect for use with Lazy Raider!

Sorry, but I get pretty excited about stuff like this =)

GO ROBOTS!
 
Apoc said:
Movement isn't targeting.

If you're using tank targeting, I highly suggest you leave it alone. (I may add an option to allow you to deal with targeting yourself, though I suggest leaving it as-is unless you're raid tanking.) It will automatically switch to targets its losing threat on. (It should only be including targets actually in combat with the party, so I'll have to get more info on the issue reported by loevstroem.

@Jon310; I wrote the Instance version of prot. Feel free to implement PVP/World versions. (Check the Context attrib on the func)

Edit; just added tank target disabling. Not tested, so lemme know if it works
Click to expand...

I guess disabling tank target functionality will temporarily fix the problem for now, however the code is really great in dungeons, so a fix would be awesome!

My logfile from last night is rather large, because of all your Singular debug stuff, so I uploaded it to my server: http://adego.dk/09-09-2011_00_33_4288Log.txt

Please let me know if I need to explain the problem better, or if I can help reproduce the issue or test a fix. By repeating my self there's certain mobs once in a while that the bot will target for some unknown reason. This can be mobs out of sight (in the other end of the instance - fx. Hadronox *search this name in the logfile*), or can be a flying dragon.. I'll report back if I notice more screwed up cases..

Regards
 
To elaborate a little on the problem with tank targetting, I took another run in The Nexus.

The problem seems to occur with:

  • Hostile targets
  • Targets not attackable (Azure Skyrazor in this example, and Hadronox is not attackable to begin with afaik)
  • The range of the unit does not seem to matter (both units were targetted by the bot, even tho miles away)

Why is this a problem?
Using automatic tank targetting this causes a huge problem, since the bot will repeatably try to target the "bugged" unit (i don't know how it's prioritized), and hereby ignore the units of the pack it's fighting with..

I attached another a screenshot for explanation. Log again cannot be uploaded due to size, and I'm unable to connect to FTP right now.

azure_skyrazor.webp
 
Are there any temporary workarounds for the "Boss hit box is big so CC won't attack unless standing inside of him" problem?
 
Zacharybinx34 said:
HEY Apoc !

Bobby has implemented an awesome feature in his ShamWOW Custom Class - the ability to start the next cast RIGHT before the current cast finishes - its called [Account for Lag]

Would it be possible to make Singular default do this for every class? That would DRAMATICALLY speed up dps rotations. Of course, it should probably be an advanced option to check - since the user would have to turn this on in game as well by checking Wow's Lag 'Lag Tolerance' option under [Combat] in [interface options]

I think this would be amazing! My fury warrior's rotation would be near perfect for use with Lazy Raider!

Sorry, but I get pretty excited about stuff like this =)

GO ROBOTS!
Click to expand...

Singular already does this. :)

I'm fairly sure Bobby just added a toggle for some built-in stuff on HB. (For a few releases, HB has automatically supported the lag tolerance stuff. It will cast "early" by default, with some overrides to turn the behavior off)

@Zacharybinx34; I'll add the workaround now. Gotta remember what I did first!
 
You must log in or register to reply here.
Back
Top