QUOTE
One problem... THEY CAN'T! Got it? That would be IMPOSSIBLE. See, I M P O S S I B L E.
Reasons? Simple.
Explain how they can detect if a map was either made with Staredit or SCMDraft.
There's no difference since SCMDraft is based on Blizzard's code for making maps. The same goes for every other map making utility out there.
Also another reason, if they had some new type of format, it would be easily gotten used to.
Actually they could detect it,
tiles were supposed to be written with other tiles accenting the other tiles paired up, as it is supposed to be. There are always terrains that are on the left side, and terrains on the right side.
In effect tiles are SUPPOSED to be placed a certain way and they could detect that there are cerrtain terrains that are SUPPOSED to be together, they are paired together. Nowadays, we are using doodad terrains to place as tiles. These can be detected.
I have never seen the original editor place bogus terrain before NEVER. I read about the possible glitches of the original editor, and it said it was a 1/1000000 chance of a bogus terrain appearing. (bogus meaning, two terrains that are not supposed to be paired up.)
Proedit, StarForge, and all external programs do write in a different format.
Most times, it deals with the protection by adding Hex Strings to it. Thus changing the file encrpytion itself.
StarCraft can detect this...
Trust me, people have tried to create SUPER protectors, but ended up skrewing themselves over when StarCraft could no longer read the file due to the fact that it couldn't read within the "back door" left for the program to "understand" the map scenario.
Now shuddup... okay? IMPOSSIBLE is possible (in this case.)
And I was just saying you guys... geez....