Locked For Editing

[viiva]

Blizzard has integrated a kind of map protection in GE's publishing feature.
You're able to check 'locked for editing', which I suppose locks your map for further editing by unwanted people.

Now, I don't know alot about map protection, but is there anyone who can elaborate on the security of this feature? How 'strong' is it? Will we be needing a third party map protector anyway?

I think it's likely it'll get bypassed some day, but hopefully that day will be in the very distant future.

Publishing

 

[Mille25]

im also interested in the security of this protection.

would be good if someone could look at it

 

[mjllonir]

What I want them to look at is why it is so buggy and glitchy, and fails 100% of the time I try to publish my map.

It keeps saying Constructing Header File Failed or Transmitting Header File Failed, which I am still wondering what these are...

 

[tagg1080]

It says in a blizz post that the protected ones are impossible to open with the editor, by anyone, and that is permanent.

The game can still open it, which means that someone might find a way at some point, but I bet they got pretty tricky with how they did it.

 

[viiva]

It would be cool if they had some kind of password system which would allow some people (project members) to open it.

 

[tagg1080]

It would be cool if they had some kind of password system which would allow some people (project members) to open it.

Or you can just keep a copy on your comp that isn't protected?

 

[Mille25]

It says in a blizz post that the protected ones are impossible to open with the editor, by anyone, and that is permanent.

impossible? id be careful with this word

 

[tagg1080]

impossible? id be careful with this word

Well, the game can still open the map, meaning that all the data can still be accessed.

BUT.

Considering that they are making this feature, and have probably planned it from the start, I am pretty sure that at the minimum a modified editor will need to be used to open them.

I have no doubt we will be able to eventually, but it will hopefully take a long time.

Hell, they might even change the way it is done periodically just to mess people up!

But that might be asking for too much, lol

 

[PurplePoot]

What I want them to look at is why it is so buggy and glitchy, and fails 100% of the time I try to publish my map.

It keeps saying Constructing Header File Failed or Transmitting Header File Failed, which I am still wondering what these are...

Pretty sure reading comprehension helps here.

http://forums.battle.net/thread.html?topicId=25026453020&sid=5000

 

[mjllonir]

I already read that and I already made the changes. I'm speaking of another problem, it says that the default values are incorrect of some sort.

 

[PurplePoot]

You may also want to look into the fact that BNet has been unstable since Friday.

 

[Akkernight]

In theory all that needs to be done is use a tool like OllyDbg or CheatEngine, and with it keep an eye on what the SC2 process is doing, and then try to play a protected map and see what's going on

 

[Dr Super Good]

All editor dependant data will probably be missing, as such you can not load it in the editor. Inorder to submit a map you will need to load it in the editor. Thus it does not stop people hacking a map, but it stops them distributing a hack outside of singleplayer. Even if they do restore the edtior only data there are probably detection methods in place which will automatically reject an attempt to upload a spoof of the map.