Specifically in the ingame mods menu - if mod A optionally depends on mod B, and some version of mod B, having a too-old version of mod B causes mod A to fail to load. This is fine, but the problem is that it gives no visual indication - or even a message in factorio.log - that mod B failed to load due to a dependency problem; the relevant optional dependency of mod A is marked in orange, not red.
A sample of this is an old version of KSPower I am using (older than 0.2), which causes MoreBobs to fail, yet shows no "missing dependency" error:
[0.16.51] Mod dependency failures do not give any notice
Re: [0.16.51] Mod dependency failures do not give any notice
Thanks for the report however I can't reproduce what you describe. When I set a dependency as needing a version newer than what's available it shows red - as expected.
Can you please upload a minimal set of mods that reproduces the error?
Can you please upload a minimal set of mods that reproduces the error?
If you want to get ahold of me I'm almost always on Discord.
Re: [0.16.51] Mod dependency failures do not give any notice
http://www.mediafire.com/file/85o78gm53 ... o.zip/fileRseding91 wrote:Thanks for the report however I can't reproduce what you describe. When I set a dependency as needing a version newer than what's available it shows red - as expected.
Can you please upload a minimal set of mods that reproduces the error?
I should also mention the same happened with my dev version of RubberBelts, which is 0.0.1 in the /mods folder. (See this issue: viewtopic.php?f=49&t=56333&p=332540#p332540 )
This is the reason for the problem I was having and we discussed on Discord a few days ago.
Re: [0.16.51] Mod dependency failures do not give any notice
Ok, It had to be an optional dependency that wasn't met to show up wrong.
It's now fixed for 0.17.
It's now fixed for 0.17.
If you want to get ahold of me I'm almost always on Discord.