Hey, quick question. I just finished my map, dled Uberation, opened the map, clicked Uberate etc etc, protected it. I then went to play it, got a whack load of errors, it started printing out the names of my switches then. . . ended in a draw. Now I know the map worked before protection. . . any thoughts as to why my map exploded?

Hey, quick question. I just finished my map, dled Uberation, opened the map, clicked Uberate etc etc, protected it. I then went to play it, got a whack load of errors, it started printing out the names of my switches then. . . ended in a draw. Now I know the map worked before protection. . . any thoughts as to why my map exploded?

[color=#1af]If I remember correctly, Uberation 3 was very buggy. If I were you, I'd use ProEdit to protect it. I don't know of any protection methods that are out that protect against OSMap, but if you know of one, that's what I'd use :P Overall though, if someone knows what they're doing, it's gonna be impossible to keep them out of your map, so you might as well just use some simple protection method to keep out the noobs.[/color]

If I remember correctly, Uberation 3 was very buggy. If I were you, I'd use ProEdit to protect it. I don't know of any protection methods that are out that protect against OSMap, but if you know of one, that's what I'd use

Overall though, if someone knows what they're doing, it's gonna be impossible to keep them out of your map, so you might as well just use some simple protection method to keep out the noobs.

Are there any other ways? XTra editor crashes on me. . . .

Are there any other ways? XTra editor crashes on me. . . .

[quote=name:NerdyTerdy][color=#1af]Overall though, if someone knows what they're doing, it's gonna be impossible to keep them out of your map, so you might as well just use some simple protection method to keep out the noobs.[/color][/quote]This. Uberation 2 is good. If I were un-lazy I'd finish TinyMap which protects as a result of immense compression.

Quote from NerdyTerdy

Overall though, if someone knows what they're doing, it's gonna be impossible to keep them out of your map, so you might as well just use some simple protection method to keep out the noobs.

This.

Uberation 2 is good.
If I were un-lazy I'd finish TinyMap which protects as a result of immense compression.

If you really want the best compression, I would try ProEdit, OS Map(yes, it compresses...), OS Map 2, Uberation 2, Uberation 3, and Starforge, and see which one gives the smallest filesize without any gameplay corruption.

If you really want the best compression, I would try ProEdit, OS Map(yes, it compresses...), OS Map 2, Uberation 2, Uberation 3, and Starforge, and see which one gives the smallest filesize without any gameplay corruption.

Most idiots on Bnet dont even know what OSMap is. So Proedit or Uberation would be the way to go from stopping petty map theves.

Most idiots on Bnet dont even know what OSMap is. So Proedit or Uberation would be the way to go from stopping petty map theves.

Which is why you should just try out all of them, IMO, the only reason for protection is A: Maximum compression, and B: Keep out most Bnet newbs. Each protector does something a little different, so try them all out and use the best one depending on the map.

Which is why you should just try out all of them, IMO, the only reason for protection is A: Maximum compression, and B: Keep out most Bnet newbs. Each protector does something a little different, so try them all out and use the best one depending on the map.

[quote=name:NerdyTerdy][color=#1af]Overall though, if someone knows what they're doing, it's gonna be impossible to keep them out of your map, so you might as well just use some simple protection method to keep out the noobs.[/color][/quote] Exactly! If StarCraft can read the map as valid, it can be unprotected by some method... The unprotection method that I use is "Unused Unprotector 4" It will unprotect anything because you have the option to either use or not use the "Strom.dll" for the unprotection. In some older protected maps, I used "Map Stats" for some reason to see something in it and it came up as saying it had over 10k+ triggers. Is this what some map protection programs do? They just give a false amount of triggers so that the editor crashes on start up of the map?

Quote from NerdyTerdy

Overall though, if someone knows what they're doing, it's gonna be impossible to keep them out of your map, so you might as well just use some simple protection method to keep out the noobs.

Exactly! If StarCraft can read the map as valid, it can be unprotected by some method... The unprotection method that I use is "Unused Unprotector 4" It will unprotect anything because you have the option to either use or not use the "Strom.dll" for the unprotection.

In some older protected maps, I used "Map Stats" for some reason to see something in it and it came up as saying it had over 10k+ triggers. Is this what some map protection programs do? They just give a false amount of triggers so that the editor crashes on start up of the map?

No, MapStats is a bit glitchy, and that might have been an odd side-effect.

No, MapStats is a bit glitchy, and that might have been an odd side-effect.

[quote=name:Brontobyte][quote=name:NerdyTerdy][color=#1af]Overall though, if someone knows what they're doing, it's gonna be impossible to keep them out of your map, so you might as well just use some simple protection method to keep out the noobs.[/color][/quote] Exactly! If StarCraft can read the map as valid, it can be unprotected by some method... The unprotection method that I use is "Unused Unprotector 4" It will unprotect anything because you have the option to either use or not use the "Strom.dll" for the unprotection. In some older protected maps, I used "Map Stats" for some reason to see something in it and it came up as saying it had over 10k+ triggers. Is this what some map protection programs do? They just give a false amount of triggers so that the editor crashes on start up of the map?[/quote] [color=#1af]This isn't an unprotection thread. I still really hate it that people totally disrespect the wishes of mappers by unprotecting their maps. When I said that if someone knew what they were doing, they could get into your map, I didn't say it was a good thing. To me it was more like saying, if someone [i]really[/i] wants to kill you, there's not much you can do to stop them. Obviously not so dramatic, just a melodramatic comparison :P[/color]

Quote from Brontobyte

Quote from NerdyTerdy

Overall though, if someone knows what they're doing, it's gonna be impossible to keep them out of your map, so you might as well just use some simple protection method to keep out the noobs.

Exactly! If StarCraft can read the map as valid, it can be unprotected by some method... The unprotection method that I use is "Unused Unprotector 4" It will unprotect anything because you have the option to either use or not use the "Strom.dll" for the unprotection.

In some older protected maps, I used "Map Stats" for some reason to see something in it and it came up as saying it had over 10k+ triggers. Is this what some map protection programs do? They just give a false amount of triggers so that the editor crashes on start up of the map?

This isn't an unprotection thread. I still really hate it that people totally disrespect the wishes of mappers by unprotecting their maps.

When I said that if someone knew what they were doing, they could get into your map, I didn't say it was a good thing. To me it was more like saying, if someone really wants to kill you, there's not much you can do to stop them. Obviously not so dramatic, just a melodramatic comparison

[quote=name:Brontobyte][quote=name:NerdyTerdy][color=#1af]Overall though, if someone knows what they're doing, it's gonna be impossible to keep them out of your map, so you might as well just use some simple protection method to keep out the noobs.[/color][/quote] Exactly! If StarCraft can read the map as valid, it can be unprotected by some method... The unprotection method that I use is "Unused Unprotector 4" It will unprotect anything because you have the option to either use or not use the "Strom.dll" for the unprotection. In some older protected maps, I used "Map Stats" for some reason to see something in it and it came up as saying it had over 10k+ triggers. Is this what some map protection programs do? They just give a false amount of triggers so that the editor crashes on start up of the map?[/quote] PROEdit's protection used to randomly add some fake CHK sections since SC only uses either the last or the first one (I don't remember which). The fake sections had corrupted data, maybe that's what is messing the stats program.

Quote from Brontobyte

Quote from NerdyTerdy

Overall though, if someone knows what they're doing, it's gonna be impossible to keep them out of your map, so you might as well just use some simple protection method to keep out the noobs.

Exactly! If StarCraft can read the map as valid, it can be unprotected by some method... The unprotection method that I use is "Unused Unprotector 4" It will unprotect anything because you have the option to either use or not use the "Strom.dll" for the unprotection.

In some older protected maps, I used "Map Stats" for some reason to see something in it and it came up as saying it had over 10k+ triggers. Is this what some map protection programs do? They just give a false amount of triggers so that the editor crashes on start up of the map?

PROEdit's protection used to randomly add some fake CHK sections since SC only uses either the last or the first one (I don't remember which). The fake sections had corrupted data, maybe that's what is messing the stats program.

[quote=name:Clokr_]PROEdit's protection used to randomly add some fake CHK sections since SC only uses either the last or the first one (I don't remember which). The fake sections had corrupted data, maybe that's what is messing the stats program.[/quote] Maybe. I just remember seeing 10k+ triggers and my jaw dropped. I knew it had to be something with the protection, because 10k+ triggers would be something like 1mb or even more of a file. Oh well.

Quote from Clokr_

PROEdit's protection used to randomly add some fake CHK sections since SC only uses either the last or the first one (I don't remember which). The fake sections had corrupted data, maybe that's what is messing the stats program.

Maybe. I just remember seeing 10k+ triggers and my jaw dropped. I knew it had to be something with the protection, because 10k+ triggers would be something like 1mb or even more of a file. Oh well.

[quote=name:Clokr_]PROEdit's protection used to randomly add some fake CHK sections since SC only uses either the last or the first one (I don't remember which). The fake sections had corrupted data, maybe that's what is messing the stats program.[/quote]Yeah. I didn't do much to take that into consideration. Nobody has told me yet which sections replace and which sections append in the event of a duplicate. >.> In my experiences Ube3 does bad things, unless it has been fixed.

Quote from Clokr_

PROEdit's protection used to randomly add some fake CHK sections since SC only uses either the last or the first one (I don't remember which). The fake sections had corrupted data, maybe that's what is messing the stats program.

Yeah. I didn't do much to take that into consideration. Nobody has told me yet which sections replace and which sections append in the event of a duplicate. >.>

In my experiences Ube3 does bad things, unless it has been fixed.