Dunatank's Warrior CC - An Arms/Fury/Protection CC

go buy a cheap gun or something and see if it will pull with that... another thing you can try is change pull distance to 5 yds in the Hb settings

if neither of these 2 options work lets us know thanks

 

You should have Charge from level 3 onwards.

 

Excellent work on 3.0. I do wonder if Manaflask is correct about Fury TG in 4.3 since there are rumors regarding to the 2-set of tier 13. Manaflask doesnt mention anything about that, looks like they simply ignore it.

 

Sweet, thanks gonna test it later tonight to see if i can do higher dps =) thanks!!

 

they dont mention your tier bonus cause its self explanatory, just use inner rage when it is up rather than for spam cleaves.... it allows more left over rage and hs on board, more dps- really what any class wants is their 4 pc and i can tell you right now ours is pure awesome when it procs.

pvp arms is pretty solid fixed everything i asked, and piercing howl works great
TG priority is wrong though its doing slams before Raging Blows and thats a major loss in dps .. (based this off a dummy test) 5mil test - almost sometimes actually rb doesnt even get off cause its bouncing back n forth between CS BT > SL > BT > SL

 

Agreed that its self explanatory, but that also means it's not implemented in this CC. It doesnt change this CC's awesomness, but it does make it "incomplete".

 

possibly with 3.1 and the new ui i know he did mention it that he would put it in as a setting to be enabled.

 

Still the same. It brings up HB error reporting window, when I skip, it takes me to the class config UI but it's messed up cuz there are no settings and everything is blank and stuff

 

did you hit "start" prior to clickling "Class config"?

 

Those leveling as Prot do not.

 

than buy a gun

 

Seriously, if you don't like this CC, don't use it. We spend our free time on developing this - for free!!
If you don't appreciate our work, you should probably try coding a "better" CC yourself.
Have fun

Edit: Try looking through all versions from v0.1 on - you'll see a whole lot of great changes. This CC was originally designed to be a 85 prot only CC, without any targeting code. People liked our work, so we decided to keep developing - even though none of our devs plays a warrior anymore.

Edit2: When coding your own CC, respect our rights of owner- and authorship.

 

Is Anybody else still getting the "Too close" error on charges?

 

...I DO develop. I also like feedback on WHAT I develop. I never once said this was a bad CC. This CC is awesome. There was a flaw, I pointed it out. I figured you, as a developer, would want to know if there was a flaw in the code of your CC. But apparently not. Sorry for reporting said flaw. No clue why reporting it was such an issue to be taken so immaturely. I purely stated that pre level 20 as prot it doesn't pull and stands there confused. I could've said "OMFG THIS CC IS SO SHIT IT JUST STANDS THERE DOIN NOTHIN WTFBROLRN2CODE"...But I didn't. 'Cause that's not true. This CC is awesome, and you've put a lot of hard work into it. It's the reason I'm even leveling a warrior. I figure if the leveling portion of it is new, and there's a flaw, or a bug, you would want to know and would want to fix it, because, as a developer, I know I'd love useful reports from people using my stuff. I often preffered "Hey, here's a glitch" to "Awesome CC! Thanks!" Because it gives me room and opportunity to grow upon the work I've done, and often times those bug submissions lead to whole new ideas and features within the product.

If you're going to be developing for anything in your life past this, expect to hear bug reports. They're nothing personal, and shouldn't be handled as such. As a developer I get giddy and can't WAIT to report something to another developer if I find something in their code that's somewhat off. After all the 3.0 file I downloaded ends in "BT" which I can only assume means Beta Testing. If you're beta testing, wouldn't you want this sort of information? I'm trying to help you, the developer, to better your work. If it were the business world, I'd do the same thing. And had you have blown up like you did in your previous post, you would've lost business because of poor customer relations.

All in all...Awesome CC, Whether you want to hear it, or not, I'm using it from level 1-85 and I'm reporting anything along the way, and beyond. What you choose to do with said received information is all on you. If you want to better your work and fix it or add something, awesome for you I'll do my best to be more thorough and more helpful.

EDIT:

If you've already previously stated this for version 3.0, there's only 2 things you can do.
1. Watch the first post for an update containing a fix for this.
2. Open the files and temporarily fix it until an official fix comes out for the error.

EDIT2:

The reason I ignored both of your posts is because you gave me fixes for myself, the individual user. I guarantee you someone else is going to come along with the same issue. So rather than using self fixes I wanted the message to go across to the developer so he could get a fix out for it and stop your endless chain of telling people temporary fixes.

EDIT3: Whilst leveling I often find that the character "dances" with it's target. I assume it's trying to get behind it to DPS, though I'm not sure. Also, ran this in a dungeon and so far it's running flawlessly.

EDIT4: Normally I'd be able to post proof of my previous statements in that developers WANT errors to be reported, but my phone is dead and I don't have a camera to take a picture of my signed copy of Windows 7 Ultimate (Signed by Steve Ballmer <3) that I got from posting logs of performance and different errors of Windows 95, 98, XP, Vista, and Windows 7 RC running on machines with the same system specifications.

 

logs with your errors will help debug the situation... i havent seen any logs guys; description of when where the error occurred with an attached debug log.

 

Not every bug produces a log error. If something was coded to run a certain way, and that way is flawed, then there will be 0 errors in the log and the issue will still occur.

See here: Syntax and Logic errors.

Syntax errors will produce something in the log. Logic errors will not. Everything I've posted is a logic error.

 

hey guys.....first of all I want to let you know that this is by far the best warrior CC out and IMHO the best CC i have used out of all classes.

Now comes my problem, since updating to 3.0 everytime i start bot (running in either Combat Bot or LazyRaider) and go to Class ConfigI get an error saying:
"Honorbuddy has encountered a problem.
We are sorry for the inconvience.
Parameter is not valid.
[checkbox] Ignore this error and attemt to continue.

you know the rest................

anyways when i check the box and click on Don't Send, the UI loads up but is blank with only the last 4 tabs accessable to tweak.
I have just done a fresh install and still no good
btw this also hapens on profession buddy and Allrounder bots.

if anyone has any insight into what is going on please let me know.....

Cheers

 

Yes I did. Still crashing.

 

Fresh HB install or Fresh CC install? when updating a CC you should never overwrite previous files, always fresh install updated CC files.

 

Joined LFR to test 3.0 out for first time and I find that on the first boss all it seems to do it cast demo, tclap, rend, cleave and nothing else (single target boss).

Re-installed 2.2 and notice thats having issues too now. Will post logs after i finish the run.

These are from old install using 3.0 then 2.2 i believe
View attachment 12-20-2011_12_45 PM 3884 Log.txt
View attachment 12-20-2011_12_45 PM 4868 Log.txt

This is from new HB install
View attachment 12-20-2011_1_33 PM 2148 Log.txt