...mpatibility/Krastorio2-spaced-out/items-data-updates.lua:67: attempt to index local 'artillery_turret_object_gun' (a nil value)
stack traceback:
...mpatibility/Krastorio2-spaced-out/items-data-updates.lua:67: in main chunk
[C]: in function 'require'
configurable-nukes/data-updates.lua:7: in main chunk

Hello! Thanks for the report. Will certainly look into this and have a fix out as soon as possible.

That said, do you mind sharing which version this is occurring for you with? As well, as it appears to be related to K2_SO, do you mind sharing which version of that you have installed?

So, I cannot seem to reproduce this issue. I've tried updating to the current version of K2_SO and its required dependencies, to which the game loads without issue irrespective of whether I enable the nuclear weapons category or not.

In addition to my above questions, what (if any) other mods are you using? I suspect there may be some heretofore unknown compatibility issue with another mod that is causing this issue.

K2SO is1.5.2。There are quite a few mods used, around 180+.I just tried turning off K2SO, and then this mod was able to start normally.I suspect that an option in K2SO caused the error.For example, the 'Real Weapons' setting was turned off because it conflicted with a certain mod.

K2SOsetting:off,off,off,on,off,k2,on

I unfortunately still cannot seem to reproduce this issue, at least not with just this mod (and its dependency) and K2SO (and its dependencies). It's good to know that it definitely is K2SO related, but given my inability to recreate it otherwise, I still suspect it is a potential compatibility issue with another mod. To that end, would you be kind enough to share your mod list?

The mod list has already been submitted on GitHub.

Thank you for sharing your mod list. I've found that it appears to be a compatibility issue with the "basic-artillery" mod by Pseudonymous; that is, I've been able to recreate the issue you reported when the "basic-artillery" mod is present.

Will be looking into the root issue, and hope to have a fix out soon.

With the release of version 0.8.2, this issue should be fixed.

Please do let me know if you encounter any other issues.