Did anyone to use subversion for team working on maps?
We are using it but it's a bit problematic cause if u save the map in SC2Components inside a version controlled directory, all the .svn directories get screwed.
Every time we must save the SC2Components in another directory and copy/paste them inside the svn dir... really annoying.
Did anyone find another faster way to do this?
I found another problem with the triggers file... if 2 guys work on it at the same time when I try to merge the 2 versions it gives a huge amount of conflicts and some different triggers or variables seem to have the same ID in common O_O.
Anyone got this problem too?
Commit failed (details follow):
Expected 'E:\Download\Starcraft 2\Maps\team repository\projects\CustomMap.SC2Map' to be a directory but found a file
Expected 'E:\Download\Starcraft 2\Maps\team repository\projects\CustomMap.SC2Map' to be a directory but found a file
Please execute the 'Cleanup' command.
The problem is the editor that renames the original directory into dirname.old and this directory contains all the .svn data.
The new created directory containing the map doesnt have the .svn files soo the versioning is lost.
We're using Mercurial on our team, luckily it doesn't suffer from the issue of directory renames since Mercurial doesn't drop dotfolders in every tracked directory.
We have yet to do a lot of collaborative stuff yet though, should be interesting what happens when it comes down to the merge.
The 2nd integer (after the header) in the .version file seems to be a revision number(?), which is shared between all version files. Followed up my something which appears to be a checksum of some sort? I'm just speculating though.
My guess would be, Blizzard might have used this internally for something; or the editor uses this for some consistency checking. It would be nice to see Blizzard's map editing workflow, I'm sure they're using a bunch of tools internally that we'll never have access to.
Some things we've learned when collaborating on maps:
Drag and drop the MapName.SC2Map folder onto the editor when working on it, this will prevent it from doing any folder renaming and you can save the map in-place
Map collaboration with Subversion is going to be very difficult, if not impossible. You're going to need someone coordinating the merges with Git or Mercurial. You're pretty much guaranteed to get a conflict when working together. Your best bet is to have people work on different subsections of the editor (triggers, object placing, terrain, etc)
While it's possible to work on lets say doodad placement together, it requires some delicate conflict resolution. For example I did a test where I added a bunch of doodads and my team mate did as well. I had to fix the Object id on every xml node because some id's were overlapping.
Mercurial allows you to use arbitrary merge tools, if these conflicts become harder and harder to merge I can envision writing tools that help the process; if it's even worth it before Blizzard gets around to releasing their tools.
Did anyone to use subversion for team working on maps?
We are using it but it's a bit problematic cause if u save the map in SC2Components inside a version controlled directory, all the .svn directories get screwed.
Every time we must save the SC2Components in another directory and copy/paste them inside the svn dir... really annoying.
Did anyone find another faster way to do this?
I found another problem with the triggers file... if 2 guys work on it at the same time when I try to merge the 2 versions it gives a huge amount of conflicts and some different triggers or variables seem to have the same ID in common O_O.
Anyone got this problem too?
What are the error messages?
Directory is obstructed
Commit failed (details follow):
Expected 'E:\Download\Starcraft 2\Maps\team repository\projects\CustomMap.SC2Map' to be a directory but found a file
Expected 'E:\Download\Starcraft 2\Maps\team repository\projects\CustomMap.SC2Map' to be a directory but found a file
Please execute the 'Cleanup' command.
Because .SC2Map is an MPQ file. It's expecting it to be a folder since it contains files within it. Looks like SVN has a problem with MPQ's.
The problem is the editor that renames the original directory into dirname.old and this directory contains all the .svn data.
The new created directory containing the map doesnt have the .svn files soo the versioning is lost.
We're using Mercurial on our team, luckily it doesn't suffer from the issue of directory renames since Mercurial doesn't drop dotfolders in every tracked directory.
We have yet to do a lot of collaborative stuff yet though, should be interesting what happens when it comes down to the merge.
There are some strange files called .version in the uncompressed map. Do you think blizzard will release a sort of versioning program?
The 2nd integer (after the header) in the .version file seems to be a revision number(?), which is shared between all version files. Followed up my something which appears to be a checksum of some sort? I'm just speculating though.
My guess would be, Blizzard might have used this internally for something; or the editor uses this for some consistency checking. It would be nice to see Blizzard's map editing workflow, I'm sure they're using a bunch of tools internally that we'll never have access to.
Hoping they will release this tool if it really exists O_O
They did say they'd make it easy for multiple map authors.
Some things we've learned when collaborating on maps:
While it's possible to work on lets say doodad placement together, it requires some delicate conflict resolution. For example I did a test where I added a bunch of doodads and my team mate did as well. I had to fix the Object id on every xml node because some id's were overlapping.
Mercurial allows you to use arbitrary merge tools, if these conflicts become harder and harder to merge I can envision writing tools that help the process; if it's even worth it before Blizzard gets around to releasing their tools.
The huge problem is that the Object file contains soo many data like units, doodas, points, etc