When I try to update one of my dependencies in 2.0.4 it just hangs forever on 'Checking Dependency References' until I finally get frustrated and ctrl-alt-delete out of the editor. Updating a dependency used to take a few seconds, now it either takes a ridiculous amount of time (I waited over 6 minutes before I snapped) for which I do not have the patience, or it just doesn't work at all.
Its problem that it doesnt recognize that the local file and on bnet file is the same. And it adds it as different mods. So that happens. If you see that local or bnet file is empty fields press cancel. I found that after connecting to bnet and looking into dependencies to know when that online dependency is downloaded (black, not grey out text.), after that waiting a minute or to with opened dependency window or something like such action you can add bnet file easily without any map breaks, or dependency waiting.
when loggin into bnet in editor. before publishing go to dependency window and look when mod is downloaded to your pc (mod name text is colored black), but dont choose it or accept changes. Close dependency window (cancel) and open it again, wait a minute with opened dependency window. And then try choosing the mod file on bnet with that lastest version, IF local file field is empty after choosing the mod file published on battle.net, cancel and try repeating process again. Otherwise you should be able to publish without any dependency checks waiting or any change in logs of message window (that may say that your Game Variants are fucked or any other errors).
I don't know. I tried to do exactly what you said and it still checks dependency references forever after I click OK. Either I still don't understand what you are telling me to do or it just doesn't work.
And we clearly see that your local files for mods are empty that why it checks forever for it.
When you press and adding the mod from bnet in the same window there is tab (top of the window) for local file too choose (it must be in StarCraft II\Mods folder). You need too choose the local file for that same mod link you using on bnet.
I just said that when I add the local file it still does the same thing. And besides even if that did work it's a really obnoxious way to work anyways since my local files are constantly changing and I don't want to store them in the required folders.
When I add the local file the field is not empty, but it also doesn't fix the problem. It checks the references indefinitely either way. The only method I have found for getting around the problem is to delete my triggers and then add them again after doing the update. Everything in my map appears to work fine so I am not sure what the problem with references is.
I feel bad for you but I am also kind of glad I am not alone.
The good news is Blizzard asked me to send them my map so they could take a look at it and maybe figure out what is going wrong. So hopefully they will find a solution!
In the mean time you can still update your dependencies by copying all your triggers, deleting them, updating the dependencies and then pasting the triggers back in once they are done updating. It's a pretty tedious a long process if you have a lot of triggers (it goes really slow... even slower in the HotS editor than it was in WoL) but at least it gets the job done.
Here is a screenshot of the problem with the local file in place.
Well other two mods dont have local files. I would suggest trying to make everything into one mod file, maybe its too much effort but still, not seems like you have something to lose.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
When I try to update one of my dependencies in 2.0.4 it just hangs forever on 'Checking Dependency References' until I finally get frustrated and ctrl-alt-delete out of the editor. Updating a dependency used to take a few seconds, now it either takes a ridiculous amount of time (I waited over 6 minutes before I snapped) for which I do not have the patience, or it just doesn't work at all.
Yeah I tried it again and let it hang for 20 minutes. It's definitely messed up.
yeah, same.
Its problem that it doesnt recognize that the local file and on bnet file is the same. And it adds it as different mods. So that happens. If you see that local or bnet file is empty fields press cancel. I found that after connecting to bnet and looking into dependencies to know when that online dependency is downloaded (black, not grey out text.), after that waiting a minute or to with opened dependency window or something like such action you can add bnet file easily without any map breaks, or dependency waiting.
Here is my post on sc2 blizz forums http://us.battle.net/sc2/en/forum/topic/7924144167
I don't understand what you are telling me to be perfectly honest. Can you take some screenshots?
Please has anyone found a solution for this problem? It's happening in both WoL and HotS. I don't understand what TwoDie is suggesting I do.
when loggin into bnet in editor. before publishing go to dependency window and look when mod is downloaded to your pc (mod name text is colored black), but dont choose it or accept changes. Close dependency window (cancel) and open it again, wait a minute with opened dependency window. And then try choosing the mod file on bnet with that lastest version, IF local file field is empty after choosing the mod file published on battle.net, cancel and try repeating process again. Otherwise you should be able to publish without any dependency checks waiting or any change in logs of message window (that may say that your Game Variants are fucked or any other errors).
I don't know. I tried to do exactly what you said and it still checks dependency references forever after I click OK. Either I still don't understand what you are telling me to do or it just doesn't work.
Do you use online and offline dependency? You can have 2 links per dependency: offline and online.
Maybe that fixes it... =/
Else, I would try to clear the cache folders in "C:\ProgramData\Blizzard Entertainment\StarCraft II\Maps\Cache"
It does the same thing when I try to use a local file. Clearing the cache didn't seem to do anything.
I made a video of the problem just in case people don't understand it based on my description.
@rtschutter: Go
And we clearly see that your local files for mods are empty that why it checks forever for it.
When you press and adding the mod from bnet in the same window there is tab (top of the window) for local file too choose (it must be in StarCraft II\Mods folder). You need too choose the local file for that same mod link you using on bnet.
I just said that when I add the local file it still does the same thing. And besides even if that did work it's a really obnoxious way to work anyways since my local files are constantly changing and I don't want to store them in the required folders.
attached file
Adding the local file does not fix the problem.
so you local file field is always empty (to all mods)? if no then im useless. If yes thats the problem should be of yours.
When I add the local file the field is not empty, but it also doesn't fix the problem. It checks the references indefinitely either way. The only method I have found for getting around the problem is to delete my triggers and then add them again after doing the update. Everything in my map appears to work fine so I am not sure what the problem with references is.
Here is a screenshot of the problem with the local file in place.
I too have ran into this problem...
I feel bad for you but I am also kind of glad I am not alone.
The good news is Blizzard asked me to send them my map so they could take a look at it and maybe figure out what is going wrong. So hopefully they will find a solution!
In the mean time you can still update your dependencies by copying all your triggers, deleting them, updating the dependencies and then pasting the triggers back in once they are done updating. It's a pretty tedious a long process if you have a lot of triggers (it goes really slow... even slower in the HotS editor than it was in WoL) but at least it gets the job done.
Well other two mods dont have local files. I would suggest trying to make everything into one mod file, maybe its too much effort but still, not seems like you have something to lose.