OK.
with 1.2, SC2BW is no longer a modified map. it is now a full blown mod.
thanks to blizzard size restrictions for map/mod files. my map now contains these SC2Mod Files.
SC2BW_-_Custom_Assets_1.SC2Mod (Imported Models/Textures)
SC2BW_-_Custom_Assets_2.SC2Mod (Imported Models/Textures)
SC2BW_-_Data.SC2Mod (All the Game Data. Units Stats and all that)
SC2BW_-_Protoss_Music.SC2Mod *******
SC2BW_-_Terran_Music.SC2Mod
SC2BW_-_Zerg_Music.SC2Mod
******* (ignore Protoss Music, too many dependencies and the map crashes)
These mod files are best placed inside the Starcraft II Folder
..\StarCraft II\Mods\
then theres the maps themselves, maps can be placed anywhere on your HDD. OK.
now you will learn about dependency hell.
![[image loading]](http://imgur.com/28Ej7.jpg)
so. going by this diagram. you see the map file. for example lets say Grand Line. uses the Dependency SC2BW Data.
SC2BW has 4x Dependencies. Custom Assets 1/2 and the 2x Music
Dependencies are published FIRST. so you would start with Custom Assets and Music. then Publish Data. THEN publish the map.
Here is what Dependencies should look like for SC2BW_-_Data.SC2Mod
![[image loading]](http://imgur.com/Bk36T.jpg)
Here is what Dependencies should look like for the Map File.
![[image loading]](http://imgur.com/5Ye3x.jpg)
Notice the version number on these screens. if you re-publish a dependency and it goes to version 1.1. you will have to open SC2BW Data and update the dependency to the new version and re-publish that. then again. opening the map file and updating the new version AGAIN and re-publishing. pain in the ass. i know.
so to clarify.
1) Publish Custom Assets/Music SC2Mod Files first.
2) then add all of them as Dependencies in the Data SC2Mod and publish that.
3) then open the map and add the Data as a Dependency. publish the map.
if correctly done. it should all work.
common problems that i've encountered.
if you open one of the maps in the editor after doing all the steps above. sometimes the map looks blank. that is no minerals/vespene/doodads. this is because the dependencies have failed to load. typically because you are not logged into battle.net. login. close the map. re-open it. if that fails. close the editor. re-open it. login to battle.net. open the map. this is purely a visual problem. you can publish with this problem and it'll be fine.
the other problem is when updating dependency versions. sometimes the editor gets confused and thinks you want to use 2 different versions of the same dependency. save it. close the map. re-open it. it should be ok now. ALWAYS MAKE SURE YOU HAVE THE LATEST VERSIONS IN YOUR DEPENDENCIES.
that should be it. im awful at explaining things in real life so this is probably no different. i'll upload the mods and maps to sc2mapster very soon. good luck.