Why? Oh Why? Would you rip pieces of the bot API out with no warning?

[wired420]

Yeah... So 1.9.5.5 broke my entire Custom Class apparently. Will most likely be HOURS before I can figure it out. Only coder of HB thats at home that I have on MSN is asleep. The other one is on vacation in a far far away land and drunk. Would be helpful if I could get a hold of the other coders MSNs as I'm a noob to C#. Don't get me wrong. I've figured a lot of stuff out on my own most wouldn't and I'm learning quickly.

Starting to see why the other CC coders are pissed off all the time. You take api functions such as WowUnit.Buffs, and Disable caching of buffs. You add a new version. And you mark it stable.

Now I know many other programming languages and this is NOT how a project should be managed. The old versions should be left in for one or two versions before being taken out or disabled.

How can you claim something is stable when its not been tested under heavy use. You can't. This is exactly the kind of stuff that caused questing to get so bugged up in the first place.

I guess some other Custom Class devs had a heads up as they get Beta versions of HB before its released. But theres some of us without that kind of access. So we're just screwed when you rip pieces of the bot out.

All in all things are getting better with Honorbuddy. But theres no way you can call a new function stable when only a limited few have used it.

Please stop doing this. This is as bad as deleting HB1 from forums when its doing 20k exp/hour more than HB2.

I don't know who exactly the project manager is and I don't mean this as a flame, but you really need to stop the coders from removing pieces of the API in the same version that a completely different function is replacing it. This is NOT considered stable, and once again it completely screws those of us working on Custom Classes that don't get pre release beta copies.

Once again. Please don't be offended by this post. I'm half blind, have one eye sealed shut with a patch over it, on pain killers, and may seem like an asshole at the moment, but this is totally supposed to be constructive criticism and not a put down of any sort.

 

[Cittidel]

I don't code (interested, but haven't done much beyond creating profiles), but I can really understand your point of view. :/

 

[Lt.Leon]

Same here.

 

[wired420]

Well. I've wasted several hours now testing to figure out that they did away with several things in WoWUnit API and dumped them all into one function. Which is fine. Makes coding easier. It would've been nice to have seen something somewhere that said this is what was being done.

Now... theres two extra requirements for a CC to compile now. I have no clue what they are, or what they are used for. So it makes it so I'll have to spend another half day testing, when it could've easily been put in a post somewhere and taken up 2 to 4 lines at most in an example. Instead. I'll spend a half a day wasting time trying to come up with what I need to use them for...... This is immensely frustrating that changes aren't posted somewhere more regularly. Every change to the API should be documented somewhere. Not all new things would need to be documented. But if you add new requirements for the compiler, or change something old into something new. This SHOULD be posted somewhere. Maybe it is and I just don't have access as I don't have access to the copies of HB like other coders do before they are released.

As of now I'm thinking of saying screw my CC until I can get a coder on MSN and just going to the beach all day and getting a nice sun burn to go with my bleeding eyes.

 

[wired420]

Ok. So I use Partial Classes to separate my CC into different files for organizational purposes. Makes it much easier for me to find things when I need to fix a small bug.

So I have

        public override WoWClass Class { get { return WoWClass.Rogue; } }
        public override string Name { get { return "Shadowstrike 2.0.0.0 - By wired420"; } }

With the rest of my defines in the bottom of my config.cs file.

Now honorbuddy 1.9.5.5 when it compiles this, expects these to be in every piece of the partial class for some reason. Now if I add this to every file right below the partial class it compiles, but I get warnings for EVERY single function I call through out the entire CC, and they fail to actually work.

On another note, This compiles to a DLL with 0 errors and 0 warning on both linux and windows....... This is currently coded to compliance standards and should work.......

I don't know what got broke in the compiler but its apparently no longer linking partial classes together. Can a coder please verify this before my little brain boils and explodes?

Edit: BTW, I've been banned from WoW for 2 weeks without any money to get new accounts and part of that time I've been off due to health issues. This compiled 100% perfect back in version 1.9.5.0. So something between then and now has broken this.

 

[fpsware]

I do agree with the little to no warning.

Fortunately, its only taken me about 20 minutes to adapt The One CC to the 1.9.5.X changes. But again, some advanced heads up would have been appreciated.

 

[Mordd]

Took 2 minutes for me to update. I dont see the issue. If you are using Visual studiuo and reference the HonorBuddy exe upon release it will tell you what needs to be changed. If you need a heads up just ask hawker and he may be able to provide you with the info.

 

[fpsware]

Don't get me wrong, I get pre-release beta's to use/test. But still, some advanced warning of major changes would be nice. But on a whole, it didn't effect me too much.

 

[wired420]

Took 2 minutes for me to update. I dont see the issue. If you are using Visual studiuo and reference the HonorBuddy exe upon release it will tell you what needs to be changed. If you need a heads up just ask hawker and he may be able to provide you with the info.

I've gotten the api stuff fixed. Now the CC just plain won't compile. It wants certain over rides in every part of the partial class, which breaks everything else. Its not possible to code it like that and have it work. I don't know what happened to the compiler but this isn't something that changed in the code or can be changed in the code. It breaks compliance standards and breaks every line of the entire CC if you do what its asking. Trust me I tried just for shits and giggles. For some reason when it compiles its not recognizing that I'm using Partial Classes and putting them together. Its compiling each one as a separate class which isn't what it should be doing. Visual Studio and which ever version of compiler I got on my linux box both compile 100% error and warning free. Its JUST honorbuddy freaking out.

 

[wired420]

Ok.... So I got it working... It shouldn't work this way... But it is.... lol... Afro Engineering for the win... Leave it to me to do something that totally shouldn't work but yet it does. lol

 

[Mordd]

Add me to MSN, I can help.

 

[namaze]

Wired420 double posted twice in his own thread!!! Glad you got it working by the way.

 

[Keanu]

It's about the same with the profiles. I am back after a month of WoW absence and HB is bitching while parsing the profiles.

 

[CodenameG]

i couldnt care, but really why change something so small as the name Buffs, or Auras? Visual studio has been complaining for a while now about the spellmanager changes, but that's still working. the only thing left to fix is the problem with my wandIsCasting code. but im going to have to give it to nesox, or someone else to try and fix it. so that means that its going to be a while before the CC is functional again.

 

[wired420]

Wired420 double posted twice in his own thread!!! Glad you got it working by the way.

Lol. I have one eye sealed shut. The other has gotten infected too and is swelling, and I'm on demerol. Plus I tried to delete my other posts and the forum is ignoring my delete button under edit lol. I'm in just all sorts of pain and problems this morning

PS) I don't care about post counts lol. I asked tony to delete my entire old thread for Shadowstrike 1.x.x.x and he moved it to archives instead of lowering my post count lol. Would've lowered my post count by probably a 100 if he did it my way

 

[hiromatsu]

This could all be solved by a in depth "change-log". The whole point of a change log is to show what changes to the code base were made and the effect it will have.

 

[MaiN]

i couldnt care, but really why change something so small as the name Buffs, or Auras? Visual studio has been complaining for a while now about the spellmanager changes, but that's still working. the only thing left to fix is the problem with my wandIsCasting code. but im going to have to give it to nesox, or someone else to try and fix it. so that means that its going to be a while before the CC is functional again.

Because that little change makes it a lot easier for new people. Having 'Buffs' cover both buffs AND debuffs is NOT self-explanatory like it should be.

 

[CodenameG]

Because that little change makes it a lot easier for new people. Having 'Buffs' cover both buffs AND debuffs is NOT self-explanatory like it should be.

yea, i asked nesox, and he gave me the lowdown on it, not that i think ill be using it to dump buffs, or whatever, but speed is always good i guess.

 

[xvii]

Now you know why I stopped supporting what was arguably the best rogue CC ever created. (mut mut)

 

[CodenameG]

Now you know why I stopped supporting what was arguably the best rogue CC ever created. (mut mut)

now you have to compete with wired. and hes doing a bang up job with it too.