Ok im neutral here but i got something to say
many people use map protection in the wrong ways.
The main argument is to avoid "map stealing"
hmph talk about ego if makers would stop being as egotistic as the stealers there be no need for such a progam cus makers dont care
On the other hand the only time i support map protection is wen their r large or complex trigger that the average person cant figure out
for example (rp-urban warfare) is a horrable map and theres no reason to protect is(example one build named marina and there no water)
Also the "map stealers" set a bad name for ppl who actually unlock for good purposes
i only support map locks if they used right and not for egotistical means
we just dont want people stealing our good maps and making it stupid
This isn't very serious...
>>Lite Discussion
If they steal the map and make it stupid, then I am with map protection. But if they steal the map for a good cause and make it better, then I'm against it. But the person should jsut create their own version instead of stealing it.
I can see why some people wouldn't want someone to take credit for their hard work if they made a battlenet map, so I don't blame them for it. Plus, it encourages you to learn things for yourself instead of just copying what you open up in an editor.
All of my released maps are unprotected. I don't mind if people look at my maps to learn things. I submit all my maps to the well known starcraft sites so anyone with common sense will see that I made it first. However, I DO protect maps that I give people for testing. But I'm aware that some people know how to get around it, so as an added measure, I slightly alter each copy I give out for testing. That way, if it surfaces somewhere, I'll know who did it. You can never be too careful.
Unprotecting for education = good sometimes.
Unprotecting for stealing = always bad.
Map protection is definitely a good thing. Now with the release of Trigger Viewer, people don't have that "unprotecting-to-look-at-triggers" excuse anymore.
Without protection, maps tend to get rigged, altered by people and become crap, stolen, etc.
I'm totally for map protection.
Even if they do not have any intent for stealing it, the decision to do anything with the map is ultimately up to you. Since it's your map, you have the right to decide what to do with it. If someone wants to modify it, ok you can give them the unprotected copy. If they want to learn from it, sure you can give them the unprotected copy. If they want to steal it, sure you can just give them the unprotected copy. The point is that all decisions must be made by you. And with the map protection, it gives you that authority.
map protection is very good. especially since the noobs rig it and add stupid versions of it.
but it does come with a down side. i use proedit to protect my maps and for some reason it kills my text.
Hey, here's an idea:
WRITE COHERENTLY
Maps are protected to keep other people from making stupid unwanted changes, and thus having endless versions/useless rigging/trigger fark ups/etc.
And I guess also because DLK is around.
If there were no one in the world who stole credit and screwd up maps for the worst then map protection would be stupid. However that is not the case so it is usefull if you don't want anyone to mess up your map or take credit for it.
QUOTE(Arbitrary @ Dec 24 2005, 05:18 PM)
Hey, here's an idea:
WRITE COHERENTLY
Maps are protected to keep other people from making stupid unwanted changes, and thus having endless versions/useless rigging/trigger fark ups/etc.
And I guess also because DLK is around.
[right][snapback]388846[/snapback][/right]
Dark_Lunatic_K?
He was actually a friend of mine. We made a map together (which turned out to be somewhat ok but failed to spread.) We use to have each other mutually on our friendslist but he took me off because of inactivity and his ever-growing f list.
Map Protection is a good thing, we just hate people who'd like to download and leave, we even hate people who has map UNprotecters, good thing that Clokr_ and Yoshi_da_Sniper helped our map protection, thanks to them.

The original version of bounds was unprotected, because I thought I could trust people, but then I saw a modification of my map that completely sucked. Bottom line: Map Protection is your Friend.
QUOTE
Map protection is definitely a good thing. Now with the release of Trigger Viewer, people don't have that "unprotecting-to-look-at-triggers" excuse anymore.
Without protection, maps tend to get rigged, altered by people and become crap, stolen, etc.
Voyager said it all. I'm getting bored.
If you have a map that is protected and you want to edit it,
ASK THE MAKER.
If you want to learn from the triggering,
USE TRIGGER VIEWER.
If you want to do anything else, either you're a noob or don't bother.
This kid is just upset because he cant look at maps. Thats all there is to it. Its not stupid.