info.json handled differently by game and modportal

[Bilka]

Hm. Maybe i'm looking at it from the wrong perspective. I see the "example" as something that a beginner can copy/paste into his file and use it and it actually works correctly. But without a dependency to the base mod it's technically incomplete, as every mod depends on base and most are incompatible if you so much as jump back ~5-10 minor versions. Granted it's a very nitpicky nitpick, but my nit-picking-kit has tools for all the small jobs too ;).

The example info json also depends on base. Again, the default dependency is the base mod. The only way to depend on literally nothing is to use "dependencies": [].

[eradicator]

The example info json also depends on base. Again, the default dependency is the base mod. The only way to depend on literally nothing is to use "dependencies": [].

Read the paragraph again, and now i understand what you're saying. But when i removed the dependencies node completely (not just empty array) i do get "None".

dependency.png (4.16 KiB) Viewed 920 times

I did just notice that the mod manager doesn't allow to disable base anymore though, so it's even more nitpicky than i expected.

[Bilka]

Read the paragraph again, and now i understand what you're saying. But when i removed the dependencies node completely (not just empty array) i do get "None".

Yep, if the mod just has the default dependencies (aka you didnt set any), it will show as "None", that's 100% intended.

[eradicator]

Read the paragraph again, and now i understand what you're saying. But when i removed the dependencies node completely (not just empty array) i do get "None".

Yep, if the mod just has the default dependencies (aka you didnt set any), it will show as "None", that's 100% intended.

It also shows "None" if i give it an empty array. So from the outside i can't see the secret difference between the two. In any case i think most mods need to enforce a minimum base minor version. My mods definetly won't run on 0.17.0 anymore :D.