Dependencies and extension mods are two different things altogether.
Dependencies are sort of like libraries that a map or mod (or even several maps or mods) can access, so that data can be used by multiple maps without having to redo them.
An extension mod is a new feature that allows someone in-game to play a custom map (not arcade) with your extension mod. So, for example, say you wanted to play any blizzard melee map with campaign units thrown in or all units are cloaked, etc., then you would use an extension mod to make it happen.
What are the real differences?
and is it really as easy as ticking the 'allow extension' button when publishing a dependency mod to work as an extension?
I'm really wanting to use my mod as an extension, but I created it as a dependency initially, and don't want to lose all the work I've done so far.
@XViper: Go
Dependencies and extension mods are two different things altogether.
Dependencies are sort of like libraries that a map or mod (or even several maps or mods) can access, so that data can be used by multiple maps without having to redo them.
An extension mod is a new feature that allows someone in-game to play a custom map (not arcade) with your extension mod. So, for example, say you wanted to play any blizzard melee map with campaign units thrown in or all units are cloaked, etc., then you would use an extension mod to make it happen.
Can I still use my dependency mod as an extension?
@XViper: Go Yes, you need to mark is as an extension so it can be found in the exetension mod list.
Hence my second question (2nd paragraph of first post). Just wasn't sure it was going to be that easy ;P (nothing else is!)
<Delete please>