This idea is based off of 2 assumptions that could easily be wrong. 1.) There are EUD's that can crash starcraft while being played, and, 2.) That can crash starcraft editors as well.

The idea is easy enough. Your done with your map, you have a backup copy, you place a unit in the centre of view when you first open up your map in an editor. You then look away from this area ( say a corner of your map ) and put an EUD in place that will crash the game/editor whenever this unit is looked at. Save your map under a release version, and your done.

Now, in theory, if anyone tries to open your map, it will crash the editor. The only problems I see with this is crashing people actually trying to play your map as well, which seems easily defeated with fog of war.

As far as this being in the centre of your map, and taking up a part of the map youd want people to play in, after the game starts, simply remove the unit and the crashing portion is over. Because triggers don't activate when you first open a map in an editor ( as far as I know ), this will make the game completly playable except to those who are map hacking when the game starts, and protect that version of your map from any tampering, even if YOU wanted to tamper with it, but thats why you made that backup, right?

If this has been though up of before, or if im wrong in my assumptions, I'm sorry. I'm still new to the idea of EUD's, but this seemed feasible.

triggers are NOT executed in the editor. -> Your idea failed.

I'm still wondering about those new korean protection methods that have their strings deleted if they are unprotected by UU2, or the newest type which makes the map unopenable completely.

What do you expect, they're Asian.

Zhuinden, I'm fairly sure that those maps you posted were simply flukes, there are a bunch of english maps that are the same way, you can't do it for every map though.

I'm sure that something causes it, it cannot be a mere coincidence that the last few versions of the korean maps I uploaded here have that (Athlit, WoE v42- string deletion / WoEv42+ complete unopenability after UU2)

Map protection -> FAILS
I hate people not sharing their stuff; it's so... egoistic!
But anyway, it's their choice
Thanks for pissing me off when I want to watch at some triggers, though

If you could, can you place a unit that when opened, it will go away when saved? ON ANY EDITOR? You can then use EUD's to detect the position of a unit. If the EUD = invalid, display text: Game invalid. And crash. And you can hardwire that EUD into every single trigger (copy and paste ftw!). So they would have to go through all the triggers (or if they are smart, select all, cut, paste, replace all of that trigger with a space ).

I think you get my theory?

I don't think there is such a unit. But a while ago I had had the idea to put "Made by <whatever>" as the Leaderboard display and use an EUD to detect the leaderboard display, and if it says something else, fuck up the map. One thing I thought of disguising it as an anti-maphack trigger. (You should add some way to prevent different operating systems and patches from activating the fuck-everything-up trigger, tho.)

@payne: Most people wouldn't object to you looking at triggers, they just protect stuff to stop other people from saying they made the map.

I know two things
Map Protection has not yet reached its limit.
If it can be read by Starcraft, it can be unprotected.

So, if you want to guarantee nobody will steal or look at your map, select it and hit DELETE, then YES to the dialog box.

There's various new Korean protection methods that do a lot of wierd stuff.

However any method of protection is merely exploiting a bug in the unprotector.

But you can make it really annoying to steal maps. Convoluted triggers, especially those that involve EUDs, that break when something is changed are a good example of this. One idea I had a while ago is using an EUD to read the Leaderboard display or force names, and if it isn't your name, fuck up the map some how. Of course, then patches (well, major patches) and maphack (and non-windows computers, I think) break it.

I know all this. I consider scrambling a protection method. People should avoid the use of EUD conditions as it is incompatible with mac users, which are more numerous than you think.

Thanks for not adding anything to the topic.

Does anyone know how this is done? I wouldn't mind adding it to any maps I make. I actually ran into a map today that did this.

You can open maps that use this method so it's protection is useless (unless you want to protect from b.net noobs.) Take a look at this thread for the best protection IMO Thread