Fury Unleashed I - The best you can get! (Arms, Fury & Protection supported)

Nom будем ждать очень.

 

Soo when I follow the SVN instructions as posted on the second post on this thread I get this message and am unable to select "Fury Unleashed" as a CR for my warrior. I have copied and pasted my Log.


[22:50:27.383 D] Activity: Initializing Routines
[22:50:27.385 D] Reloading AssemblyLoader<ICombatRoutine> - [RoutineManager] ReloadRoutineAssemblies called.
[22:50:28.804 N] Compiler Error: c:\Game\Honor Buddy\Routines\Fury Unleashed\Interfaces\GUI\FU_GuiExtentions.cs(21,25) : error CS1501: No overload for method 'GetValue' takes 1 arguments
[22:50:28.804 N] Compiler Error: c:\Game\Honor Buddy\Routines\Fury Unleashed\Interfaces\GUI\FU_Interface.Designer.cs(67,30) : error CS1061: 'System.Windows.Forms.PropertyGrid' does not contain a definition for 'CommandsBorderColor' and no extension method 'CommandsBorderColor' accepting a first argument of type 'System.Windows.Forms.PropertyGrid' could be found (are you missing a using directive or an assembly reference?)
[22:50:28.804 N] Compiler Error: c:\Game\Honor Buddy\Routines\Fury Unleashed\Interfaces\GUI\FU_Interface.Designer.cs(70,30) : error CS1061: 'System.Windows.Forms.PropertyGrid' does not contain a definition for 'HelpBorderColor' and no extension method 'HelpBorderColor' accepting a first argument of type 'System.Windows.Forms.PropertyGrid' could be found (are you missing a using directive or an assembly reference?)
[22:50:28.804 N] Compiler Error: c:\Game\Honor Buddy\Routines\Fury Unleashed\Interfaces\GUI\FU_Interface.Designer.cs(74,30) : error CS1061: 'System.Windows.Forms.PropertyGrid' does not contain a definition for 'SelectedItemWithFocusBackColor' and no extension method 'SelectedItemWithFocusBackColor' accepting a first argument of type 'System.Windows.Forms.PropertyGrid' could be found (are you missing a using directive or an assembly reference?)
[22:50:28.804 N] Compiler Error: c:\Game\Honor Buddy\Routines\Fury Unleashed\Interfaces\GUI\FU_Interface.Designer.cs(75,30) : error CS1061: 'System.Windows.Forms.PropertyGrid' does not contain a definition for 'SelectedItemWithFocusForeColor' and no extension method 'SelectedItemWithFocusForeColor' accepting a first argument of type 'System.Windows.Forms.PropertyGrid' could be found (are you missing a using directive or an assembly reference?)
[22:50:28.804 N] Compiler Error: c:\Game\Honor Buddy\Routines\Fury Unleashed\Interfaces\GUI\FU_Interface.Designer.cs(80,30) : error CS1061: 'System.Windows.Forms.PropertyGrid' does not contain a definition for 'ViewBorderColor' and no extension method 'ViewBorderColor' accepting a first argument of type 'System.Windows.Forms.PropertyGrid' could be found (are you missing a using directive or an assembly reference?)
[22:50:28.804 N] Compiler Error: c:\Game\Honor Buddy\Routines\Fury Unleashed\Interfaces\GUI\FU_Interface.Designer.cs(466,27) : error CS1061: 'System.Windows.Forms.PropertyGrid' does not contain a definition for 'CommandsBorderColor' and no extension method 'CommandsBorderColor' accepting a first argument of type 'System.Windows.Forms.PropertyGrid' could be found (are you missing a using directive or an assembly reference?)
[22:50:28.804 N] Compiler Error: c:\Game\Honor Buddy\Routines\Fury Unleashed\Interfaces\GUI\FU_Interface.Designer.cs(469,27) : error CS1061: 'System.Windows.Forms.PropertyGrid' does not contain a definition for 'HelpBorderColor' and no extension method 'HelpBorderColor' accepting a first argument of type 'System.Windows.Forms.PropertyGrid' could be found (are you missing a using directive or an assembly reference?)
[22:50:28.804 N] Compiler Error: c:\Game\Honor Buddy\Routines\Fury Unleashed\Interfaces\GUI\FU_Interface.Designer.cs(473,27) : error CS1061: 'System.Windows.Forms.PropertyGrid' does not contain a definition for 'SelectedItemWithFocusBackColor' and no extension method 'SelectedItemWithFocusBackColor' accepting a first argument of type 'System.Windows.Forms.PropertyGrid' could be found (are you missing a using directive or an assembly reference?)
[22:50:28.804 N] Compiler Error: c:\Game\Honor Buddy\Routines\Fury Unleashed\Interfaces\GUI\FU_Interface.Designer.cs(474,27) : error CS1061: 'System.Windows.Forms.PropertyGrid' does not contain a definition for 'SelectedItemWithFocusForeColor' and no extension method 'SelectedItemWithFocusForeColor' accepting a first argument of type 'System.Windows.Forms.PropertyGrid' could be found (are you missing a using directive or an assembly reference?)
[22:50:28.804 N] Compiler Error: c:\Game\Honor Buddy\Routines\Fury Unleashed\Interfaces\GUI\FU_Interface.Designer.cs(479,27) : error CS1061: 'System.Windows.Forms.PropertyGrid' does not contain a definition for 'ViewBorderColor' and no extension method 'ViewBorderColor' accepting a first argument of type 'System.Windows.Forms.PropertyGrid' could be found (are you missing a using directive or an assembly reference?)
[22:50:40.991 D] [RoutineManager] Routines have been reloaded. Current class-specific list:
[22:50:40.991 D] PureRotation 2.1.5 v1.0.0.0
[22:50:40.991 D] Singular v3.0.0.2742 v3.0.0.2742
[22:50:40.991 D] YourBuddy MoP BT IR 2.1.3 - Warrior v0.0.0.0

 

Read the FAQ in first post. You need .net FrameWork 4.5. It's free and download link is in the FAQ.

 

Hi Nom, what can I say, fantastic work!!

I have a question (or an observation really I guess) I have Battle Shout selected as my default buff, but sometimes I see its casting Commanding shout. does the CC 'sense' or look for pre existing buffs and if it finds another strength buff (like the DK's Horn) use Commanding shout instead?

 

nomnom, how can i ever repay you for all your hard work, Tyrael and Fury Unleashed is the best combo ever made, without it i probably wouldn't even play wow anymore, I'm able to beat people in dps that are 30 il above me and warriors are what around 12th best for dps? Sincerely a grateful user.

 

You can always like the first post, rate the thread 5 stars and buy me a beer via a small donation on PayPal !

Actually, I've noticed the same. I think it's a bug in HonorBuddy, as I've read through every line of Commanding Shout code and I simply cannot find an error in it. I've also heard that a Druid routine is experiencing something familiar with a different spell ... We'll see what happens. If you'd like, please test it for me with version 118 (Zipfile in the first post), and let me know if it has the same issue. There is no smart code in my routine regarding shouts.

Also, good that you're using the developers version. That one is in my opinion miles ahead on the current release. I'm actively updating that one also, so update on regular base!

 

I second this...I went into dungeons in almost full blue gear as a tank and I am always first on dps with over 50k(sometimes 60k+) which is almost impossible for my gear and spec...! This is by far the best cc I ever used and I have all classes at 90 and played them all with their respective popular CCs...

EDIT: Are you ever thinking release a cc for another class?

 

Hi Nom,

As requested I have reverted to V118 and ran around killin stuff (like before with V125 SVN V775 which switches between battle and commanding shout). As you can see in the log file Commanding shout is not cast at all in V118! weird or what!! hope the log helps you sort this VERY minor 'bug'

 

We've already released for another classes (melee mostly) -->

Shammy (Enhancement / Elemental)
YBMoP-BT-Rogue (Going to remake into Waldo new core)
Death Vader (Death Knights Unholy / Frost)

 

Just testing latest Ver (SVN 776) and the battle/commanding shout is still switching

 

Can confirm switching of shouts with latest dev-rls.
Also: It's now buffing the shouts permanently, when cd is down. I liked it much better the way it was before where it only buffed precombat when I targeted something...

 

@nom

I miss this routine and my warrior so much. Got banned just after I got it past 520 and 2 LS normal kills. The CR has nothing to do with the ban, its awesome!

But Blizz still sux monkey balls!

 

Hi I have just started using this as a seasoned prot warrior. I have had it running on a dummy tonight and Im liking the DPS out put, but currently...

No disarm - as mentioned in another post


Ill take this to ToT tonight and see how it compares with the CC I normally use.

 

Disarm will be added asap , as soon as I've fixed the shout bug ...

Get your acc back!

Yep, its annoying .

I know, I have an idea regarding a fix but not implemented yet.

Thanks for the report.

Not me, but alxaw releases routines using the core of this routine. So they should be very good .

 

why do we have to choose between shield block and barrier now? I thought you were going to implement a logic to chose when to use which?

 

Making a logic for choosing shield block and barrier (automated) seems a bit tricky to do.

You would need to first make a list over bosses where shield block or barrier is best to use (priority)

Then you would need to make the routine to do shield block or barrier depending on which boss you're currently facing.

So in the end, it's better for you to choose which is best to do against each boss yourself as a user, read and find out which is best against which boss in ToT or similar.

Please enlighten me if I've gotten this wrong nomnomnom

 

Great work nom, Dev SVN 779 shout is working perfectly ty for all your hard work!! I knew you could do it

 

Internal revision 126 is released as zipfile and on the release SVN.

Core:
* Code cleanup has been done & removed Encounterspecifics.
* Added SequenceCast methods (Thanks Ama).
* Added Non-Cached Aura functions (HasAura).
* Improved Unit caching - Updated caching for NearbyRaidMembers, RaidMembersNeedCryCount, AttackableMeleeUnitsCount, InterruptableUnitsCount, NearbyAttackableUnitsCount & NeedThunderclapUnitsCount.
* Added float for CalculatedMeleeRange (Only the method, not used yet).
* DefaultBuffCheck updated with !Me.IsChanneling.
* Revamped _preCombatBehavior - Much more reliable now and should fix the shout bug.
* Added BarrierBlock ENUM and added None ENUM to shout section.
* Cleaned the Hashset lists.
* Updated logging - Debug logging might be obsolete now ... Not sure if I should remove it.
* Removed PlayerPower LUA and updated all PlayerPower calls to Me.CurrentRage.
* Removed Stance Switching hotkey - Its off-gcd so useless hotkey. Macro it if you need it.
* Added Special hotkey - Only used for Protection. See protection section to know what it does.
* Removed the "thousands" RemoveAllKeys & RegisterKeys and replaced it with one simple call on save.
* Moved BotEvents to its own file.
* Revamped racial usage. Support added for ALL racials!
* Revamped the InitializeCaching() Composite - Less code thus faster.

General:
* Class Racials % to General GUI section - Use racial on % HP or MP - Shared with all specs.
* Moved Lua.StartAutoAttack to a more general position. Only one call now for all specs.
* Moved InitializeInterrupts() to a more general position. Only one call now for all specs.
* Made fadingtimers more flexible. Integer added - No more set MS.
* Added extra booleans - IsImpaired, IsLazy & IsSick
* Added glyph check for Hindering Strikes.

Arms:
* Added Slows & Snares section to the GUI.
* Added Enable Intimidating Shout setting.
* Added InitializeArmsPreCombat to fix Shout bug.

Fury:
* Added selection for Tier 4 Abilities - AoE (Usage of Tier 4 ability during AoE).
* Added Enable Intimidating Shout setting.
* Added InitializeFuryPreCombat to fix Shout bug.
* Added Colossus Smash to the AlmostDead Decorator.

Protection:
* Revamped entire Prot GUI settings.
* Added numerous extra settings!
* Added an option to always taunt if !G.TargettingMe (Unit not targetting you).
* Updated Shield Block and Barrier method. You can select via GUI which one is used OR use the Special Hotkey to switch between Block and Barrier.

Loads of hours are invested into this routine by myself. Any donation would really be appreciated!

Glad that I got it resolved. Thanks for testing m8!

Correct. If someone has a good idea to automate it, let me know via PM.

Sorry. I simply do not know of a good automated method to do so. Open for suggestions though!

 

Fantastic Prot changes Nom!
I think allowing the Tanks to choose between Barrier/Block is the best idea, It's just so situational - Hotkey method is the best alternative.

 

What can I say? the best, has just got MUCH better. I dunno how you do it, what ever your drinking or smoking keep it up m8!!!!