.dll CC's Yes or No

This is quickly turning into the most exciting thread on the forum.

 

Thanks for your elaboration Bossland.

I know german law a bit (besides the dutch, english and polish one), and know how one hangs along with the other.
I have/had my fair share with mainly dutch laws (not living in Poland for nothing).

As I said I can understand your point perfectly, just trying to find a nice middle road for both sides that is acceptable without doing any concessions on security or protection.

 

Big thanks to Bossland and _MaiN for clearing that out.

Just for example:

If you could encrypt .cs files, this wouldn't help the community. Many ppl want to fix things, make it work for their purpose, want to see what the code does, as long as they release it with proper credits, or just use it for their own it's ok.

I think, if you publish something, you want that other users make use of it/help with error reports, fixed and so on. Like the OpenSource concept, otherwise you just don't publish it and you are fine.

syn3

 

My hands are tied behind my back so the way I see it, I stay or quit, and I am going to ride this roller coaster till the end. If that means 2 million rip off CCs then so be it. At least I will know in my own head that there is only one Mordd, and will always be one Mordd. Call the rip off devs a "Woder" or "Wannabe Coder".

I think I am forgeting somthing which I tend to forget when this kind of topic is brought up. Pogue is what started me. No open source Pogue, no me.

Though a sticky with etequite (I dont know how to spell it) guidelines would be nice. If you post chopped up CC's you dont belong here.

 

Glad to see you stickin' around. Would be a worse off place without you.

 

Yeah nice to see mordd staying, lets hope for the best with fpsware and his "The One".

 

He ain't going anywhere. He lives here now.

 

I would like to hear that from FPS himself before cheering.
I think FPS will consider this a major setback, and maybe even one too big to continue.

Wait for his answer.

 

Bottom line he wants to protect his code. If that is not an option he will be in the same boat as me. Deal with it or quit.

 

I don't see how anyone could write a better paladin class anyhow.

 

there is no middle road. just leave it as it is man..

 

I haven't read this full threat, but figure I'd throw my .02 cents in anyway.

Solution:

Make all CC's open source, BUT have them linked to the paid plugin system.

For example:

All CC's must be sponsored by HB2 paid plugin system (free or otherwise) So in order to USE the CC you have to have the plugin that 'authorizes the session'
CC dev makes a GREAT CC (FPS & Mordd's for example - I'll use the One in this example)

You download theOne CC
You pay the $1/month charge for the paid plugin
You can use theOne under your authorized username with the paid plugin system (assuming this is how it will work)

Now, the catch is that you can't just copy and paste the source code, because you HAVE to have an authorized paid plugin session to use it.

Another example of a random druid CC
You download the random druid CC (no fee)
You download the free plugin (no fee)
You use the no fee paid plugin system so that you are authorized to use the CC (even though its free)

This solution protects da boss because the CC is open source but also protects the CC dev because the CC MUST be sponsored by having a valid session to use it through HB2.

I am not sure I got my point across, but it is totally a viable solution if you can link the authorization of using a cc to the paid plugin system.

I think I'm going to write a cc later this week, for fun and only for PVP.

 

Okay so here is my 2 cents worth, it's going to be short and to the point.

I have made my opinion very clear to the developers; I was against the removal of DLL support in HB2. The developers have voiced their concerns and opinions over why DLL support should no longer be included. Regardless of a public poll that clearly indicates (65%) the general populace is in favour of this.

I personally feel disheartened, underappreciated and brushed aside by some of the comments and opinions expressed by the developers. I feel there has been no consideration or concession given for loyalty and dedication.

Unfortunately Honorbuddy is not a democracy (sorry Tony) it is an oligarchy at best, this is a fact we live with and our choices are simple, either accepted or move on to another bot.

I will admit my initial reaction to their rather staunch stance on this issue was to stop all development on The One CC, after calming down a little (over the last week) I realised that would have been a rather childish and a rash approach to take.

While I still disagree with the decision they made I have no choice but to accept it and move forward. Having said that The One CC will be released in the coming weeks in source code format.

 

both bossland and hawker voted no...looks like it's not gonna happen

 

Thanks for being kind enough to consider releasing "The One" CC even though you don't like the fact that you can't "protect" your hard work =/

 

Someone with more of a voice should really look at my suggestion and consider implementing it. People will be much more motivated to make quality CC's (and plugins) if they will be rewarded by the people who want to use it.

And using MY suggestion it can be built into the new feature of the paid plugin system. Like I said, HB is protected by having the source, devs are protected by having control of the cc use through authentication.

 

I understand that this change is like a slap in the face to alot of you devs out there. But I have to applaud your decision to continue with "The One". Your CC's are the best of the best IMHO and they really make HB what it is.

Once again, a BIG THANK YOU! to FPS for sticking around and making HB all that much better!