Halo Tag Converter Public Release

[Inferno]

and no it will not be made public.

We are such a awesome community.

[ShadowSpartan]

What's the harm in releasing map protection tools?

Could really do a lot to stem the demented pussy whining that arises whenever someone rips something :\

I never said there was a harm, I just don't want to release it. If somebody wants to analyze what I did and then program their own, go ahead. I highly doubt anyone will do so though.

We are such a awesome community.

I find it funny how a lot people complain about how we are a fucked up community because we protect our stuff, and now you people want a new protector?

There are very few people who would benefit from my protector. If someone truly needs a way to fix map protection for sp maps, I will probably help (like Rob with BCE).

[Inferno]

I don't protect any of my maps unless they are beta or have beta builds of tags in them. All final products are open sauce. I just find it funny that we are now protecting our protector more or less.

[Choking Victim]

I don't protect any of my maps unless they are beta or have beta builds of tags in them.

Then what the fuck do you care?

[CtrlAltDestroy]

Here's some advice for everyone:

Lighten the fuck up.

[DarkHalo003]

I never said there was a harm, I just don't want to release it. If somebody wants to analyze what I did and then program their own, go ahead. I highly doubt anyone will do so though.


I find it funny how a lot people complain about how we are a fucked up community because we protect our stuff, and now you people want a new protector?

There are very few people who would benefit from my protector. If someone truly needs a way to fix map protection for sp maps, I will probably help (like Rob with BCE).

But why wouldn't you release it? Just because you think we're acting hypocritical? The stuff y'all release is like a bunch of new toys that we want to exploit and play with outside the maps you give us, which is why we wish good maps/weapons were unprotected. Now, can I protect weapons and bipeds and not have to worry about the checkpoint screw ups? What causes the checkpoints to screw up? Protecting the scenario?

I agree with CAD.

[Choking Victim]

CAD's comment was directed at people like you. Think of it this way, a protection method is meant to protect. Open sourcing the program to protect the content is like open sourcing the protection algorithm.

If you can't comprehend that, then here's another analogy:
It's like adding a password to something and releasing the password publicly.

Get it?

[Masterz1337]

You don't even need new protection.

The only reason I want to use it, and ZTeam made it, is that we seem to have idiots every 3 months creating a scene trying to hack the maps. HEK+ has the option to not protect certain tag classes. Figure it out yourself on which ones need to be unprotected to stop string and checkpoint errors. The Zteam protector is designed to work only with CMT and Zteam tagsets anyway, it won't benefit you even if you had it.

[DarkHalo003]

CAD's comment was directed at people like you. Think of it this way, a protection method is meant to protect. Open sourcing the program to protect the content is like open sourcing the protection algorithm.

If you can't comprehend that, then here's another analogy:
It's like adding a password to something and releasing the password publicly.

Get it?

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. I'll drop this now because it seems y'all are set on your decisions. If so, let it be.

[Masterz1337]

It won't help you with SP protection.....