Factorio Forums

Will there be mod compatibility with the current blueprint mod or will it be replaced by a on-board blueprint book in 0.13?

brunzenstein wrote:the current blueprint mod

You're going to have to be a lot more specific than that.

In my opinion, there is a flaw in the info.json notation.

In Dependencies section we have things like base >= 0.12.x

Well 0.13 is > 0.12.x, so Factorio 0.13 thinks it can load mods with this dependency.

However any 0.12.x mod that requires "defines" in control.lua is going to fail.

DRY411S wrote:In my opinion, there is a flaw in the info.json notation.

In Dependencies section we have things like base >= 0.12.x

Well 0.13 is > 0.12.x, so Factorio 0.13 thinks it can load mods with this dependency.

However any 0.12.x mod that requires "defines" in control.lua is going to fail.

defines is not part of the base mod, it is (or was) part of core. putting a dependency on the base mod means... get this... that you depend on something in the base mod.

sparr wrote:

DRY411S wrote:In my opinion, there is a flaw in the info.json notation.

In Dependencies section we have things like base >= 0.12.x

Well 0.13 is > 0.12.x, so Factorio 0.13 thinks it can load mods with this dependency.

However any 0.12.x mod that requires "defines" in control.lua is going to fail.

defines is not part of the base mod, it is (or was) part of core. putting a dependency on the base mod means... get this... that you depend on something in the base mod.

So should I have put a dependency on the core?

I'm not sure how we can access items that were in defines.lua now
If I simply remove defines, then I start getting nil references

vedrit wrote:I'm not sure how we can access items that were in defines.lua now
If I simply remove defines, then I start getting nil references

Some of the objects have changed how you reference them.

I don't have that particular issue, what I do have are people posting issues that my 0.12.x mods won't work with 0.13.x Factorio. My point is that if the devs wanted to change the way we write mods in FActorio 0.13, they should have put something in the core game to stop 0.12.x mods from loading.

(Unless this is my fault and I should have put a core dependency in my mods, which I *think* is what sparr is suggesting.

For some reason, defines.events is working.
As for preventing 0.12.x mods from loading, perhaps you could do something like "base <= 0.13" in your dependencies. From testing, putting a dependency on core doesn't seem to be recognized.

vedrit wrote:As for preventing 0.12.x mods from loading, perhaps you could do something like "base <= 0.13" in your dependencies. From testing, putting a dependency on core doesn't seem to be recognized.

With 20-20 Hindsight, that's what I have should done. Bit too late now, I'm certainly not going to update my 0.12 mods with that, when the 0.13 versions are available.

Being able to have a core >= dependency would be a good way forward. A <= implies mods will work with 0.11, 0.7, 0.3 etc, which they wouldn't.

DRY411S wrote:My point is that if the devs wanted to change the way we write mods in FActorio 0.13, they should have put something in the core game to stop 0.12.x mods from loading.

They did. Mods now require a "factorio_version" separate from the dependencies. If you've got old 0.12 mods they are disabled for lack of that line.

sparr wrote:

DRY411S wrote:My point is that if the devs wanted to change the way we write mods in FActorio 0.13, they should have put something in the core game to stop 0.12.x mods from loading.

They did. Mods now require a "factorio_version" separate from the dependencies. If you've got old 0.12 mods they are disabled for lack of that line.

Thanks for that clarification. IHowever seem to have some evidence that contradicts your assertion. Can you offer further advice please?

https://github.com/DRY411S/Recycling-Machines/issues/7

I think there was a bug that *some* files of disabled mods still got loaded no matter what.

hoho wrote:I think there was a bug that *some* files of disabled mods still got loaded no matter what.

If it was control.lua files during a 'migration', that would explain it!

Nope. It's a bug in my understanding about how mods load up.