Currently while my MK5 and MK6 machines won't explode, they'll still destroy themselfes without power.
An option to disable the damage all together would be nice
Thats good to know, just did some more tests and my 5. tier and 6. tier machines do indeed explode, just takes a long time, the 4. tier ones do not take damage
-also double checked, i do have the setting set to not explode
i am on newest version , let me know if you need a save
Thank you - looking now. I usually go in with a theory, which is part of why a complete explanation is very important. I believe that you clicked the button to turn off damage as the bots were taking damage. My theory is that it did change the setting, but the internal table used to track all bots - rather than wasting cpu scanning for them, was not purged, might causing them to continue to take damage.
BUT - even if the array were not purged the check and infliction of damage would be stopped as soon as the button is turned off, so could you verify that within your game you pressed: ESC -> Settings -> Mod settings and turned off "Explode BNO Assembling Machine at 20% power" ? https://imgur.com/a/AqP2IYS
Yes that option is turned off, i just placed all 3 machines outside of my power and bot network to see if they take dmg, 4.tier didn't take dmg, 5. and 6. did.
OK - great info. If you can post your save game that may be helpful.
I appreciate the support! Please join the discord too. https://discord.gg/ghrS9vJM
My current theory is that you are playing with 2.0.6.
2.0.6 changed a variable name but didn't copy the old table to the newly named ones, this is fixed in 2.0.7.
I just tested 2.0.7 and the asm's does not take damage if the check box is turned off.
So what version ? Please provide a full log file.
I do use alot of mods but the fact that 4. tier works perfectly fine makes me think that something went wrong during the update.
I already had tier 4 machines in my save when i updated but i didn't have any tier 5 or 6 ones.
Fix:
Go into the map settings again - turn it ON then OFF.
The interface setting for the mod did not properly reflect it's setting. I suspect this was introduced in my missing a variable update in 2.0.6, then fixing in 2.0.7. You had it off, but due to the variable name change, it must have gotten initialized to true (on), and the interface did not reflect the same value that the code had.
