Halo Tag Converter Public Release

[Choking Victim]

I didn't mean open source it; I meant make an application release of it, like a new HEK+ with better portection. I'm just stating that it would be useful to have for SP use, seeing as how it seems to be getting a lot more popular now. But whatever, I'm sure if someone wants it that bad they can politely ask for it.

You don't seem to realize how strong some reverse engineers are. There are methods to disassemble an exe and even decompile it to code form to see the source code. I'm not saying it's a perfect system, but definitely do-able.

All in all, just because you don't release the source code, doesn't mean your program is protected.

[supersniper]

If you want this community to prosper then a new enhanced protector is NOT needed.
Zteam has made many programs that have helped the community so far, they have done countless hours of research as well.

And Choking Victim makes sense, why do you think Hek+ encryption is very easy to bypass now... Because people can download it, de-create it, or analyse how it works, and find a way to decrypt the protection.

I say leave it private, and if you really need it that bad contact zteam and ask nicely.

Edit: Sorry dude it was a typo, won't happen again.

[Choking Victim]

It's spelled "Choking". See user title, but thanks.

[DarkHalo003]

You don't seem to realize how strong some reverse engineers are. Hell, even with an obfuscated exe locked to only zteam members' pc's, kornman was able to reverse engineer and unlock it for use on his pc. There are methods to disassemble an exe and even decompile it to code form to see the source code. I'm not saying it's a perfect system, but definitely do-able.

All in all, just because you don't release the source code, doesn't mean your program is protected.

Alright, that makes sense now. I'm not a scripting genius yet or really involved with the outside workings of an application. I've just worked with the stuff inside it is all. But this makes more sense now.

I was implying that my last post sniper.

[ShadowSpartan]

Ok, that is enough. No more discussion of the protector. My decision stands. Let's all get back to the topic at hand, which in case you forgot, is the release of HTC.

[t3h m00kz]

Here's my grasp of the situation. From what I understand, the whole drama was caused by ShadowSpartan's comment in bold:

SPv2 will use my new map protection, the errors you mention of have been fixed, and no it will not be made public.

Which honestly, was a pointless thing to add to what he said. Let me put it to you this way, he could have gotten off saying:

SPv2 will use my new map protection, the errors you mention of have been fixed.

with alot less drama. Something like that shouldn't be mentioned unless asked, because he should know by now people are uppity about the whole ZTeam thing.

E: shit

[supersniper]

Now even though this is another version that was scrapped long ago will anyone be picking up the project to fix it and make it 100% working or is it just going to be like HEK+ with errors...

I know I would fix it if I new a thing or to about programming.

[Kornman00]

Expect something more solid and useful in the coming months

[SnaFuBAR]

Will you release the greater method by which you're protecting your SP maps?

That's up to Zteam.

Sno it will not be made public.

Seems like a pretty reasonable answer to me, muki. Perhaps you should try reading the post in context.

[t3h m00kz]

I missed it, I admit. We cleared it up over PMs.

I had a few Coronas, I was a bit out of it so I just skimmed through the thread. Honest mistake, you know how it is.

Probably should have mentioned that earlier... my bad dawgz

Expect something more solid and useful in the coming months