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

Themyscira 2.0 - Warrior CC Coming Soon (tm)

Status
Not open for further replies.
The current Warrior CC is amazing in my opinion, if you can code these improvements in then that'll be fantastic.

(Cleave capabilities please!)
 
I love the sound of this and can't wait to start using it!!

*EDIT*

It would be great if you could add the use of racials for example:

Tauren - Warstomp when there are adds or a caster
Orc/troll - When recklessness is up or something like that
Night Elf - When health is below <x>
Blood Elf - When mana is below <x> and to interrupt caster
Undead/Human - When snared etc..
Draenei - When health is below <x>

Thanks!!
 
Last edited:
You could just take a look at the combat logic of my old warrior CC and port that into a new one. The combat logic in my CC was very good, it played all 3 specs just like a human would. If you need a copy of it, let me know.
 
You could just take a look at the combat logic of my old warrior CC and port that into a new one. The combat logic in my CC was very good, it played all 3 specs just like a human would. If you need a copy of it, let me know.

Thanks Likwid. At the time I wrote Themyscira (1.0) I had played the Warrior in all 3 specs for many months. But its been so long now that I've forgotten everything about it. I just to have a play with the class again and get a few ideas how things have changed - or stayed the same. The logic in Themyscira worked well (at the time) but the new BT logic makes things a little different.
 
One thing i notice using the old version of Themyscria is when my spec is arms, it won't use bladestorm in PVP =(
 
one request id like to make it shoot. atm im getting runners that he follows into other packs. shoot could help solve his problem
 
For protection:

Spam devastate instead of heroic strike unless rage is super high, use shield slam on procs of sword and board especially. Make use of last stand + enraged regen. Thunderclap/demo shout only with 2 or more mobs, cleave with 2 or more mobs. Berserker rage to break fear, use charge AND intercept as well.

Option for commanding shout or battle shout obviously. Concussion blow on runners at low HP. Shockwave on runners also I suppose if Concussion blow is on cooldown, use shockwave if there are 2 or more mobs. shield block pretty much every cooldown. make rend a tickbox option (not really needed for normal use) use revenge EVERY time possible, seriously, revenge and Shield slam need to have top priority here. Pull with heroic throw if charge and intercept are on cooldown, otherwise use one of them. If you dont have enough rage for an intercept use bloodrage. spell reflect if you're fighting a caster (make this able to be disabled for higher level players) and the spell is reflectable. disarm should be a tick box also (with logic to only use on melee mobs)
 
For protection:

Spam devastate instead of heroic strike unless rage is super high, use shield slam on procs of sword and board especially. Make use of last stand + enraged regen. Thunderclap/demo shout only with 2 or more mobs, cleave with 2 or more mobs. Berserker rage to break fear, use charge AND intercept as well.

Option for commanding shout or battle shout obviously. Concussion blow on runners at low HP. Shockwave on runners also I suppose if Concussion blow is on cooldown, use shockwave if there are 2 or more mobs. shield block pretty much every cooldown. make rend a tickbox option (not really needed for normal use) use revenge EVERY time possible, seriously, revenge and Shield slam need to have top priority here. Pull with heroic throw if charge and intercept are on cooldown, otherwise use one of them. If you dont have enough rage for an intercept use bloodrage. spell reflect if you're fighting a caster (make this able to be disabled for higher level players) and the spell is reflectable. disarm should be a tick box also (with logic to only use on melee mobs)

Very nice feed back thanks.
 
I'm going to try a new look UI for the Warrior. Its a bit different from my usual UI. Let me know what you think. Instead of dozens of tick boxes almost all options are selectable via Drop Down boxes, and the Drop Down boxes have multiple, user friend options. This new type of UI layout will allow for considerably more options while reducing the UI clutter.

Warrior - new look UI.webp

Warrior - new look UI tab 1.webp
 
Thanks Likwid. At the time I wrote Themyscira (1.0) I had played the Warrior in all 3 specs for many months. But its been so long now that I've forgotten everything about it. I just to have a play with the class again and get a few ideas how things have changed - or stayed the same. The logic in Themyscira worked well (at the time) but the new BT logic makes things a little different.

yeah, thats the thing really keeping me from working on a different cc.. i havent taken a look at any of the new api, so i dont know anything about behavior tree or whatever. maybe ill take a look at it..

the one thing you might want to think about before getting so deep into the options .. cataclysm is right around the corner and there are going to be many changes to the way you play a warrior - in all 3 combat trees, thanks to the new talents we're getting. that being said, if you were around for WotLK release, then you know that they released a patch with all the new talents and abilities almost a month before the actual expansion was released. blizz has said that they plan to roll out cataclysm the same way. so your combat logic could be changing in as little as a month from now. just some food for thought.
 
Good UI, if some tickboxes isn't that bad or user inserted area's but it should do;) looking forward to test it for you.
 
yeah, thats the thing really keeping me from working on a different cc.. i havent taken a look at any of the new api, so i dont know anything about behavior tree or whatever. maybe ill take a look at it..

the one thing you might want to think about before getting so deep into the options .. cataclysm is right around the corner and there are going to be many changes to the way you play a warrior - in all 3 combat trees, thanks to the new talents we're getting. that being said, if you were around for WotLK release, then you know that they released a patch with all the new talents and abilities almost a month before the actual expansion was released. blizz has said that they plan to roll out cataclysm the same way. so your combat logic could be changing in as little as a month from now. just some food for thought.
There will be more than a month till 4.0 is out.
 
I'm going to try a new look UI for the Warrior. Its a bit different from my usual UI. Let me know what you think. Instead of dozens of tick boxes almost all options are selectable via Drop Down boxes, and the Drop Down boxes have multiple, user friend options. This new type of UI layout will allow for considerably more options while reducing the UI clutter.

Not quoting the images, but what is that a Bloodrage "only with adds and below 30" setting? Is that below 30 rage or 30% HP?
 
Not quoting the images, but what is that a Bloodrage "only with adds and below 30" setting? Is that below 30 rage or 30% HP?

The only reason you would use Bloodrage is to generate rage. I think the setting is self explanatory if you know what the spell is.
 
I need help with some limiting options for 'on add use' spells. If any of the below logic does not looks right let me know.

Cleave: optionally tick box do not cast unless Steeping Strikes is on cooldown. Obviously prefering to use Sweeping Strikes first (if spec'd)

Intimidating Shout: optional tick box do not cast unless Retailation is on cooldown

Retaliation: optional tick box do not cast unless Intimidating Shout is on cooldown

Recklesness: optional tick box do not cast unless Sweeping Strikes is NOT on cooldown. Will attempt to cast SS before Recklesness.

I'm trying to give as many options to limit the number of 'on add cast' spells as possible. Otherwise, you could have 2-4 long cooldown spells being cast at once. Ultimiately making them useless.
 
I need help with some limiting options for 'on add use' spells. If any of the below logic does not looks right let me know.

Cleave: optionally tick box do not cast unless Steeping Strikes is on cooldown. Obviously prefering to use Sweeping Strikes first (if spec'd)

Intimidating Shout: optional tick box do not cast unless Retailation is on cooldown

Retaliation: optional tick box do not cast unless Intimidating Shout is on cooldown

Recklesness: optional tick box do not cast unless Sweeping Strikes is NOT on cooldown. Will attempt to cast SS before Recklesness.

I'm trying to give as many options to limit the number of 'on add cast' spells as possible. Otherwise, you could have 2-4 long cooldown spells being cast at once. Ultimiately making them useless.

None of the 5 min cooldowns should require intimidating shout to be on cooldown. If I'm not mistaken both requiring the other to be on cooldown will make none of them fire. Pop the 5 mins before the fear. Fear should be the last CD used as it has the potential to bring in more adds.

Recklesness is the fury 5 min cooldown. Believe recklessness and retaliation's options should be switched. Prob just got the names switched. (Sweeping Strikes/Retaliation for arms, recklessness for fury)

Other than that it looks good.
 
Last edited:
The only reason you would use Bloodrage is to generate rage. I think the setting is self explanatory if you know what the spell is.

I was asking cause I thought it might be the bloodrage + enraged regen/last stand combination. But I see enraged regen there also, just wondering if that includes last stand or not?
 
I was asking cause I thought it might be the bloodrage + enraged regen/last stand combination. But I see enraged regen there also, just wondering if that includes last stand or not?

Oh shit... Last Stand :p I thought I was forgetting something.
 
Status
Not open for further replies.
Back
Top