Attaching a savefile with mentioned problem.
Where to find the problematic circutis:
Gleba, jellynut plantation (8 hours from the spawn), train stop "[item=jellynut] Cargo / Load"
Gleba, yumako plantation (3 hours from the spawn), train stop "[item=yumako] Cargo / Load"
Re: [2.0.34] "virtual-signal=signal-ghost" is gone without migration
Posted: Sun Feb 09, 2025 4:17 pm
by Hares
Attaching minimalistic non-SA savefile with the mentioned problem (created on 2.0.32 - latest stable):
Load on 2.0.32 - Works fine, no alerts
Load on 2.0.34 - Signal is gone w/o any migration popup, alert is fired
Re: [2.0.34] "virtual-signal=signal-ghost" is gone without migration
Posted: Sun Feb 09, 2025 4:40 pm
by Rseding91
Thanks for the report. Virtual signals do not get a popup migration message (not everything does). The "signal-ghost" was removed because the signal entity-ghost is identical.
Re: [2.0.34] "virtual-signal=signal-ghost" is gone without migration
Posted: Sun Feb 09, 2025 4:46 pm
by Hares
Rseding91 wrote: Sun Feb 09, 2025 4:40 pm
Thanks for the report. Virtual signals do not get a popup migration message (not everything does). The "signal-ghost" was removed because the signal entity-ghost is identical.
However, this causes signals to disappear. Migration is required when making a breaking changes. Removal of the mentioned signal caused my Gleba base to blackout.
Re: [2.0.34] "virtual-signal=signal-ghost" is gone without migration
Posted: Sun Feb 09, 2025 7:28 pm
by Rseding91
I’ve forwarded this to the person who merged the PR. The PR said to specifically remove this signal because the icon was the same as the entity ghost one - and so the people working on it did.
But of course this did what you’ve served and it no longer exists in saves because the icon isn’t actually used anywhere except rendering - internally it’s all different between the signals.
Re: [2.0.34] "virtual-signal=signal-ghost" is gone without migration
Posted: Mon Feb 10, 2025 3:47 pm
by Hares
For those who wonder: this JSON migration placed within your game folder works fine (keeps achievements ON)
This will replace all removed signals with the new hourglass signal, so no conflicts should be there.
Automatic migration to entity-ghost, unfortunately, is not possible.
Also note that this would only work if the savefile didn't run on 2.0.34, so you must rollback to earlier save.
Re: [2.0.34] "virtual-signal=signal-ghost" is gone without migration
Posted: Tue Feb 11, 2025 1:12 am
by Muche
As a consequence of the removed virtual ghost signal, an imported blueprint containing it will skip entities referencing it.