For more information see here Bug Report Template Build: V1.10.4 4243 Mode: Single Player Mode: Creative SERVER NAME:- SEED-ID:- If applicable: MODIFIED PLAYFIELDS:- Reproducibility:always Severity: Major (as it can permanently damage signal logic in your save-game) Type:Signal Logic Summary: Placing a Sensor at the Core location redefines value '0' Description:If you place a Sensor at the position where the core was at the start of your build, it will have default '0' as the Name of the signal set. This redefines the Value 0, that is commonly used in signal logic. Which causes you to no longer be able to use that Value (e.g. to deactivate an input in a 4x OR). See Video for how to reproduce and for the impact it has on the signal logic. Note that the effect is not limited to the one blueprint, all Value '0' in the save-game will be borked from that point onwards, so this can actually permanently damage a save file! It will even cause other Save-Files to also inherit this error, at least until all affected saves are removed and (possibly) a restart of the game is done. Steps to Reproduce: 1) Start new creative, spawn a CV Starter Block 2) Move the core away 3) Place a Sensor at the previous position of the core Screenshots, Crash Logs, any other Relevant Information or Download links:
I had this somewhere around last year too, but not caused by placing the sensor as described, iirc it was because i deleted a signal-emitting device, and that signal was used as entry for another circuit... long story short: the effect was similar, 0 was "already used" and my savegame broken. Restarting didn't help. Restarting into another savegame neither. First after i deleted all caches and all savegames (practically a fresh install) did it work again.
