He's about as likely to publicly reveal it as pigs flying. The second he reveals how it is done it can easily be reversed. I do know some of how it works, but it is not my method, and so I wouldn't feel right teaching others how to undo it, even partially.

Another thing you may want to add, SC Character Swap, is a program that swaps out characters a-o(I think) for characters only in the actual StarCraft font that look the same, however, in editors, which don't use SC's font, it makes it difficult to read, even though it looks perfectly normal in game.

For the record, Esponeo has shown me a new way of protecting maps that cannot be undone by any mere unprotector. Bypassing it requires a number of modding tools, and even then, is difficult and time consuming. I'd say if anyone has found a protection that has the least drawbacks, he has.

I don't have the specifics to re-create it, but I do have one of the specially protected maps in my possession. I am however not giving it out without his permission.

He's about as likely to publicly reveal it as pigs flying. The second he reveals how it is done it can easily be reversed. I do know some of how it works, but it is not my method, and so I wouldn't feel right teaching others how to undo it, even partially.

my method in my mind:
7. add staredit.net & your name to the map in multiple places (forces is important)

That's like saying a map can't be stolen if it's never made.

On another note, I too have a protection method that can't be beaten by any unprotector. Of course, I can't use it or give it out yet because once I do it will be easily reversed.

There is at least 1 Korean protector out there currently, that I know of, that cannot be unprotected(as of yet), honestly, most "protection" nowadays is just people managing to find bugs in unprotectors and exploiting those specific bugs.

Right but this is traditional protection. The method I'm speaking of to my knowledge has not even been considered here on SEN. I doubt the Koreans have tried it, but I have no way to know for sure.

Honestly, that's a bit of a joke, as unprotection is a simple idea, all it does is take what SC reads and put the editor's sections back in, it's quite fool proof, and my guess is that he has simply been using the wrong unprotectors, since I know that there is a relatively simple protection method that messes up both Unused Unprotector and OS Map 2, and it wouldn't surprise me in the least that this is his "amazing" protection.

Session Start (devilesk:SHMIDLEY): Wed Feb 25 01:14:59 2009
[01:14] SHMIDLEY: So I made some new protection.
[01:15] devilesk: lol
Session Close (SHMIDLEY): Wed Feb 25 01:15:38 2009


Session Start (devilesk:SHMIDLEY): Wed Feb 25 01:16:03 2009
[01:16] SHMIDLEY: My old method from 2006 still beats all unprotectors.
[01:16] SHMIDLEY: But this new one also crashes WinMPQ.
[01:16] devilesk: that's great
Session Close (SHMIDLEY): Wed Feb 25 01:16:09 2009


Session Start (devilesk:SHMIDLEY): Wed Feb 25 01:16:19 2009
[01:16] SHMIDLEY: And the map cannot be viewed properly in Hex Workshop
Session Close (SHMIDLEY): Wed Feb 25 01:16:25 2009


Session Start (devilesk:SHMIDLEY): Wed Feb 25 01:16:38 2009
[01:16] devilesk: is your method not making the map?
[01:16] SHMIDLEY: No.
Session Close (SHMIDLEY): Wed Feb 25 01:16:46 2009


Session Start (devilesk:SHMIDLEY): Wed Feb 25 01:16:51 2009
[01:16] SHMIDLEY: Would you like a copy of the map
[01:16] devilesk: later
[01:16] devilesk: pm me it
Session Close (SHMIDLEY): Wed Feb 25 01:16:59 2009

Session Start (devilesk:LEGACY WEAPON): Sat Feb 28 14:26:05 2009
[14:26] devilesk: shmidley says he has an unbeatable protection
[14:26] *** Auto-response from LEGACY WEAPON:
[14:26] devilesk: that even crashes hex editors
Session Close (LEGACY WEAPON): Sat Feb 28 14:27:28 2009


Session Start (devilesk:LEGACY WEAPON): Sat Feb 28 14:28:38 2009
[14:28] devilesk: pm'd if you want to take a look at it
Session Close (LEGACY WEAPON): Sat Feb 28 14:29:00 2009


Session Start (devilesk:LEGACY WEAPON): Sat Feb 28 17:08:34 2009
[17:08] LEGACY WEAPON: at this point
[17:08] LEGACY WEAPON: I don't really cafre
[17:08] LEGACY WEAPON: LOL
[17:08] LEGACY WEAPON: considering these things
[17:08] LEGACY WEAPON: 1) New protection methods are being discovered but the % of maps using them is less than 1
[17:09] LEGACY WEAPON: 2) Unprotection is relatively widespread so most people have access to these tools
[17:09] LEGACY WEAPON: 3) People on battle.net don't care what name is on the map, which was the main goal of protection in the first place
[17:10] LEGACY WEAPON: 4) Nobody is really making maps worth unprotecting anyways
[17:10] devilesk: lol
[17:10] LEGACY WEAPON: because the main purpose of map unprotection is to learn things we didn't already know or understand
[17:10] LEGACY WEAPON: everything now is understood, everything that needs to be understood can be unprotected
[17:11] LEGACY WEAPON: nothing new is worth unprotecting can be unprotected
[17:11] devilesk: heinermann said a while ago that
[17:11] LEGACY WEAPON: therefore there's nothing to worry about
[17:11] devilesk: our knowledge of maps is still incomplete
[17:11] devilesk: like stuff about the sections still isn't known
[17:12] LEGACY WEAPON: like what?
[17:12] devilesk: idk
[17:12] LEGACY WEAPON: lol
[17:12] LEGACY WEAPON: the point is
[17:12] LEGACY WEAPON: at this point, it doesn't really matter
Session Close (LEGACY WEAPON): Sat Feb 28 17:12:52 2009

First of all, ask yourself this question: Is it truly necessary to protect my map?

because protecting your map will stop people from editing and spreading your maps. Although that's what you seemingly want to avoid, allowing people to edit your map will make your map popular, as when they make the changes, they'll try to spread it too. If you're lucky, the editor will give you credit. If not... it's a risk you have to take...
Another thing is that if your map is super complicated (which I assume would be because.. well.. you're a korean-fanatic...), then normal b.netters won't be able to figure out ur triggers and edit it...
Finally, the one thing that makes people protect maps are people that take it and replaces your name with his... Now this is a sensitive area, as people would be very upset if the stolen version got spread, and no one 'acknowledges' your work... But you must first realize that if your map is very popular, then the original version shall prevail. If your map is unpopular, then no one's gonna steal it. It is the mediocre maps that are in danger... Now should u settle for mediocrity? ...
Good example would be you thinking "Hero Siege" was made by "Life2Death", an infamous map stealer amongst this forum... Oh btw, he's a smart guy.. He deleted the Warrior, hoping that some idiots will think that the map originally had only 11 heroes, and warrior was added by me and thereby stealing credit. (dude who makes a funky number of "11" heroes.. plus there's a fucking SPACE at the hero selection.. indicating it has ALWAYS been set up for 12 heroes) He also tried to steal my "Snowcraft".. which was kinda a joke as he was trying to frame people on this forum... fortunately I didn't care... as the map was unpopular.. so meh~...

...Also.. if people edit your map, that's probably the most sincere form of flattery, and you should compliment yourself if they do. ( <3 Moose)

Now if you still want to protect your map, do you reallly need a crazy map protector? For me, whenever the map's protected, whether if it's just Starforge protection, or a crazy hex protection, I wouldn't touch it, as 1. it'd be too much of a hassle to unprotect it .. 2. I respect the author's decision.
Usually if u just use a wimpy protector, most ppl'd just ignore it.. unless someone's really out there to get you.. o.O .. or if your map's REALLY good (but again, if it's REALLY good.. then the original ver will prevail)

I'm still undecided about the permanently inscribing your name though. A question for unholy.. would you have used the name protection method if you'd known about it and known that temple siege would become so popular?[/color]

It would not have become as popular if he did protect it, so the question is null. It's also kind of an inside joke that Urine did protect his map by making his triggers sloppy. Messing with it would be more trouble than it's worth.

If the map crashes hex editors, why would SC be able to read it? The only way I can think of that working is if you totally corrupted the file within the operating system.