The map goes over the newish max dependencies limit blizzard added. So i figured ill remove the campaign dependencies since they arnt used exect for a few minor models.
The order of my decencies is: (if it matters)
2 normal blizzard mods
2 campaign blizzard mods
4 custom mods by me
then this i get a crazy long error massage when i try to open the map. takes over an hour to open.
Once the map is open, everything is gone. All the data, dependences, and possibly triggers.
I have a working back up version, but i still need to find a way to remove the decencies with out destroying the map.
Wow, ouch! I have no idea how things could go so wrong from removing dependencies. In the worst case, I really thought some data objects and models would go missing, this is very surprising. (I would be curious to see if the map still explodes just with a different MPQ's DocumentHeader without the dependencies )
Perhaps a simpler solution : since 4 of the mods have been made by you, could you just merge their content? Merge the data files, the Galaxy scripts, I can't see what could go wrong with that.
minor question: why do you have four custom mods?
as i understand it Mods can have other mods as dependencies, i do not understand why four would be necessary.
How did you remove the Campaign Mods? if you were using any of their contents the editor should prevent you from removing them. if you sucessfully removed them and this is the result i would attempt a save as with a different name and close and re open the new map. to see if it remains as such.
i tried 3 times, and all had the same results. Then a friend of mine tried, and it worked with out a problem. I have no idea why, but it is fine now.
I have 4 mods because 3 are loaded with a few hundred custom models, and 1 is loaded with unit sounds, icons, and 2d portraits.
edit: ok its not removing the mod that caused but changing a mod. 1 mod was locally saved and set as a dependency to the map. To upload the map of course you cant have locally saved mods. I removed the locally saved version and added the uploaded version. This is what is causing the explosion. All this mod has is .wav and .tga files, nothing else.
The map goes over the newish max dependencies limit blizzard added. So i figured ill remove the campaign dependencies since they arnt used exect for a few minor models.
The order of my decencies is: (if it matters) 2 normal blizzard mods 2 campaign blizzard mods 4 custom mods by me
then this i get a crazy long error massage when i try to open the map. takes over an hour to open.
Once the map is open, everything is gone. All the data, dependences, and possibly triggers.
I have a working back up version, but i still need to find a way to remove the decencies with out destroying the map.
Wow, ouch! I have no idea how things could go so wrong from removing dependencies. In the worst case, I really thought some data objects and models would go missing, this is very surprising. (I would be curious to see if the map still explodes just with a different MPQ's DocumentHeader without the dependencies )
Perhaps a simpler solution : since 4 of the mods have been made by you, could you just merge their content? Merge the data files, the Galaxy scripts, I can't see what could go wrong with that.
minor question: why do you have four custom mods? as i understand it Mods can have other mods as dependencies, i do not understand why four would be necessary. How did you remove the Campaign Mods? if you were using any of their contents the editor should prevent you from removing them. if you sucessfully removed them and this is the result i would attempt a save as with a different name and close and re open the new map. to see if it remains as such.
i tried 3 times, and all had the same results. Then a friend of mine tried, and it worked with out a problem. I have no idea why, but it is fine now.
I have 4 mods because 3 are loaded with a few hundred custom models, and 1 is loaded with unit sounds, icons, and 2d portraits.
edit: ok its not removing the mod that caused but changing a mod. 1 mod was locally saved and set as a dependency to the map. To upload the map of course you cant have locally saved mods. I removed the locally saved version and added the uploaded version. This is what is causing the explosion. All this mod has is .wav and .tga files, nothing else.