I'm always against protecting. Well, people keep saying that people will make edited versions, but really, unless your map is very popular, why would they bother? And triggers, half the time people protect maps that are very simple, the perfect map to learn from. The small amount of knowledge I have of triggers came from examing other people's maps, and I see nothing wrong with that.
Metal_SonicI'm always against protecting. Well, people keep saying that people will make edited versions, but really, unless your map is very popular, why would they bother? And triggers, half the time people protect maps that are very simple, the perfect map to learn from. The small amount of knowledge I have of triggers came from examing other people's maps, and I see nothing wrong with that.
Actually, that's how i learned how to edit myself too, i hijacked another map, and continued constructing it, adding new things, figuring out the old triggers, perfecting them, changing things around, adding.. etc. Eventually, only about 5% of the original triggers were left, and the terrain was totally transformed. That map never really got through on the internet anyway, as it was more for myself, to learn. Now the map is screwed, although the triggers are ok, the many patches have screwed things up, rendering me unable to fix all the harm done, and it's not worth it anyway, the map was never totally my own.
Now in turn i've got a map that is reasonably populair, but it is "protected" as a sideeffect of an optimiser. I don't mind the protection, as i don't want people to take my map and change it around. I do in every way i can try to allow people to learn from my map, so there's a note in it when opened in WE with my email, so they can send questions. I've had quite some already, and helped all those people who wanted to know something. Map protection isn't all bad, it depends on how you use it, and compensate.
There was no need of posting something like this, we all know that map protection is bad. Good in a way, but bad in another.... the most acceptable way of protection I've found is hiding the units and all the stuff in the editor except the triggers (didn't figure out how to do that yet) but I loved that way of protection. This way people can't edit the map, but look at the triggers and learn from them. All the rest of protections = crap. Blizzard should do something about this.
That's a good one. If only blizzard enabled us to open-source the triggers, but protect the map as a whole, would be neat. Do you think it would help to suggest it to them?
agreed... i am afraid of my map because it has a lot of unique triggers one way is to transform triggers to comments so the noob editors can't steal them!
The most likely reason they don't protect it Rui's way is probably for a similiar reason as the stealers, it's easy, don't get me wrong however, I am not meaning all, or criticizing, just observing and guessing, also, it could be that they consider the triggers most significent, or haven't even thought of this idea (I didn't) as the thieves probably never thought of making their own map, though I hate to compare myself to them.
for those peeps how are genuine map makers and want to know learn the triggers and make the maps themselves, this wonderful forum is the best place to start. most FAQ are posted about 10 - 20 times so if you spend half and hour reading going through all the posts you'll probably find what your looking for. or you can spend about 3 hours tring to find way of unprotecting peoples maps stumble on a porn site and lose all intrest in what you were gonna do in the first place. Plus i can guarantee nearly all maps makers who post there maps and those maps are protected will be quite happy to tell you how they did it. Protection rules. (VG n Darky are gonna whoop my ass for saying that. )