I am having an issue where it is impossible to upload my map due to multiple versions of dependency chain 3.3 and 0.0. This problem can only be solved by using the latest version of the dependency.
However I am not sure just how much the dependency can affect the map, for instance what if a new version of the dependency say if Renee decides to reduce the damage of archers by half, or remove/replace certain models from the game, which is all part of dependency development, but that could seriously break my map.
Wondering if there is a workaround to prevent dependency updates from breaking the map.
Not to pile up or get you further "down" but dependencies are a marvelous adventure, nothing more...
If you want to make your own adventure .. not an adventure through a dependency that you have no control over, then.. it is harder/longer but also what you want.
sc2 main base depdcies / wrcrft3 or nova(s) .. same thing (i must add that rene deserves more praise than anyone to succeed as he has <3 and i still cant believe it works as well as it does (his work through blizz, not his work), for how i use them that is)
i do it.. but mostly to see the models, the animations, .. to visit the library!
in a perfect world / map i'll be doing what glorn said.. uploading every lil thing manually.. so that my map has it all and i no longer gasp AS MUCH before/after every blizz patch
at one point i did my own mod .. and the "latest version mechanic" at the time made it impossible to publish the map (not kidding / no kappa).. it required for me to publish the mod/ re launch editor / open my map / it wouldn't find my mod / i d open it.. re establish the mod manually / publish .. and even that stopped working.. maybe it is better now but i'm never advising/doing that again ty
dependencies = lot of work/investment for no apparent use!
rant said.. let us see the other side of it:
all we are doing on galaxy is using a library (many libraries/platform/etc yes), let us rejoice at the fact that it is patched (while crying our selves to sleep at night) it means it is not left to rot (it will be soon though / 5 years tops id say before it does) .. it has to be patched (insert asinine sarcasm here) that is the ONLY way the clueless devs of todays industry have found to keep "control" over their platform (lol)!