Closed eglove closed 4 years ago
ghost
commented
4 years ago @eglove
It looks like those mods have updated and the specific versions required by Fallout 4 Enhanced Edition aren't available anymore. I think the modlists will need to be updated.
eglove
commented
4 years ago I see, it seems 3/4 of the FO4 modlists are unusable. (I haven't checked the 4th yet.) Maybe something could be done to work around this issue?
ghost
commented
4 years ago I (just a guy who hit the same issue, not a modder or anything) don't think any of those options are good solutions.
You might be able to edit the modlist yourself to trick it into accepting the latest versions, but it's not really worth the effort and may break unexpectadly.
eglove
commented
4 years ago Every mod should have a JSON with the version listed. If the modlist can specify a version, than the information should be available. Or, I think it would be very odd if it weren't.
Working around the issue is only a matter of either A) Checking if a modlist is viable, or B) doing the installation as much as possible and giving the user the information to allow them to choose how they want to proceed.
halgari
commented
4 years ago We had a list stability checker in place until recently when some server changes mandated that we rewrite the code. It should be back up in a few days. The server code automatically disables modlists that are known to be uninstallable. As well as auto-upgrades mods to new downloads under certain situations.
As far as allowing a modlist to continue to install even if some downloads are broken, is not something we plan on adding, or at least we won't make it an option in the UI. To few people read the documentation anyway, so they'd abuse the feature to get something to install then complain when the game crashes.
So just hang on for a few more days. I'm in the process of rewriting the server code, and as I do I'm taking care to "do it right" which while it means it takes a bit longer to code and get running, it ensures that we don't run into major problems in the future, like the one that caused this server issue in the first place.
On Wed, May 13, 2020 at 9:41 AM Ethan Glover notifications@github.com wrote:
Every mod should have a JSON with the version listed. If the modlist can specify a version, than the information should be available. Or, I think it would be very odd if it weren't.
Working around the issue is only a matter of either A) Checking if a modlist is viable, or B) doing the installation as much as possible and giving the user the information to allow them to choose how they want to proceed.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/wabbajack-tools/wabbajack/issues/828#issuecomment-628075398, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAE72HPGHKEV4LNC5BX7JGLRRK5ULANCNFSM4M7HZT3A .
-- “One of the main causes of the fall of the Roman Empire was that–lacking zero–they had no way to indicate successful termination of their C programs.” (Robert Firth)
eglove
commented
4 years ago Gotcha', thanks for the reply.
Describe the bug On multiple Fallout 4 mod lists I'm getting a failure to download when it comes to specific mods. They work fine on Nexus and I have Premium connected. This only started happening when I updated to 2.0.4.4. To be honest, I don't remember which version I updated from but it was a 1.0.x. (Unrelated request: Please add Wabbajack to Chocolatey.) ;)
Normally I would assume this is not a problem with Wabbajack but with the modlist or Nexus, but this is consistently happening. Nexus is working fine, and I have downloaded these lists on previous versions. Plus, it would be odd if they were all coincidentally failing.
Additional context F04 - I've tried SSE, Banana Split, and FO4 Enhanced Windows 10 Pro 64-bit PC Info: http://speccy.piriform.com/results/Mmbjq2SVMrXxACUkJot2ldM
Screenshots https://imgur.com/94BHXqr https://imgur.com/OZGxeSJ https://imgur.com/tOAbo7e
Logs