.dll CC's Yes or No

so with the new release I won't be able to use DarkBens demo lock .dll? If not will I be able to still use the older HB aswell so I can use the new one when I want to pvp on my rogue while still using the older one for leveling?

 

Hi

my point of view:

NO! Why?
Because:
1) Eventough some people are trustworthy, people can change anytime.
2) Yes i can't code a CustomClass myself, but atleast i can edit it to my needs, i just don't like some things, which make it looking bottish to my eyes...
3) Sometimes even the good programmers make mistakes, so you can maybe fix them, contact the CC-Dev and help him a little.

Thats what i think...

alchemist

 

Mhh well, if the HB Staff will take a look over the code and compile it, so we are prevent from rnd-code, I say give us DLL.

I understand the reasons why its better for CC-Devs and I agree with em

 

First of all I want to thank everyone that reacted so far (and that will react in the near future on this thread) for keeping it civil and open minded.
I gathered a few posts again and answered with my own opinion.

Even though the CC's are in .dll format, if u ask the developer, you get the source code.
In some cases like DarkBen's warlock, the sourcecode is posted along.

The problem is, if someone makes a change in the CC, breaks it and comes and complains in the CC release thread, the developer has no means to check if it's his released CC or a altered one by some dipstick, that "forget's" to mention he changed it.
So it would be hard to say not to support the CC when U change it because if it's a .cs file, you don't know if it's altered or not by the user.

I realise it's a long shot Tony, but nonetheless I felt that this had to be done with a poll and a civil discussion.
I for one run everything I don't trust in a sandbox (but then again I'm also not the average user I guess).
Maybe if the devs read the thread (and I know they do, Bossland voted no), they have a change of heart and reinstall the .dll support.

I would hate to see those fancy CC's move away from HB2 (it's not only the bot, but also the CC's that make the bot as good as it gets).

I hope so too. I rather use the old HB and a good CC, than a new HB with a "poor" CC.

As stated earlier.
If asked politely, the developers will hand u the sourcecode of their project, so you can change and recompile yourself in VS.
If I can do it, you can do that too.

 

I realize that they are stressed with the release, and I'm not demanding anything.
Just let em do their thing, and we do ours (as always).
Simply trying to get facts sorted and opinions posted.

Maybe for one of the follow-up releases it can be enabled if enough users are voting for the use of libraries, or it gets torpedoed if enough people vote No.

Possible Option: 1 release that doesn't allow dll's (We (HB Development) support this blablabla) and 1 release that does allow dll's (*! USE AT OWN RISK !* We DONT support this blablabla), so we can have a choice.

It's a democracy after all

 

My CC is working with HB2, but should be used as source.

OFC, the source i deployed wont work. you need a converted source, i have already done it. And helped other 2 devs to convert theyr source as well.

Only problem is that i will rewrite to settings method because for some reason it?s not working as source, it?s not saving the settings. But it?s reading the default ones from the file.

 

And my other question, will HB1 still work after HB2 is released?

 

On a sidenote.

I remember that for PhP there is a way to encrypt the file, and PhP being able to read it without problems, but that the file itself is unreadable without a proper decryption key.
Is such a thing not possible for .cs files?

something like this (for .net, it's native c++ but can't be too far apart I guess) http://www.codeproject.com/KB/mcpp/EncDecExt.aspx or http://www.eziriz.com/ <<<--- This is no advertising, merely suggesting a way to protect their work if .dll will not be allowed, don't hit me tony

I have too little knowledge to know this of C and it's derivates, but that might be a viable option too if .dll's will stay on the banlist (if this is possible at all ofcourse).
That way the source is protected, no alterations are possible by users and there's no use of .dll

Win/Win for everyone if this is possible?

 

If HB Devs wanted to keep DLL away for security reasons, they could give the CC devs that somewath they trust a Key to sing in the DLL and only accept those signed DLL.

Thats not the case, i believe the intention was to keep open coding to go on. So community itself could give support on a dead CC project (for e.g) not to mention to learn from other codes.

Open sources leads to copying. DLLs can be reverse engineered to obtain the source.

Somehow it?s frustrating to see someone receiving all credit because he made a better cake than you, and all that it did was to copy your formula and put a cherry on top of the cake.
But thats open source.

 

I voted yea. If a dev wants to protect there stuff they worked hard on they should. All there is to it and the community can't stop them from doing it either

 

Here are two replies I received when that question was asked last night:

- In your first example, you have control over verifying and posting it, whereas if someone posts it on a different website (or starts charging for it, claiming its theirs), you can't remove it as easily.
- In your second example, there are far, far more people who will take plain-text source code and post it as their own then spend X amount of time reflecting or disassembling code to claim it as theirs. It takes 10 seconds to open notepad, change a name, and repost, it may take hours (if not longer) to reflect, get the right values, fix what broke, make sure it works, etc. A little deterrence goes a long way.

 

I always say no. Open CC's are more fun.

 

I vote no, because then people can't make minor changes like if they don't wanna use that skill etc (ofc they need to have minor knowledge about c# =) )

 

Tough one it seems.
If you allow DLL's you have to sort out a system of verification.
If you dont allow DLL's you may hold back cc devs from releasing stuff and have little private groups of people cropping up using underground CC's that they dont want to release to the public, or worse, not release any at all.
The HB Devs want to protect their customers, but the CC devs want to protect their code.
Both ideally should get to do both working together.