...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:
Is Anybody else still getting the "Too close" error on charges?
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.