The deconstruction planner cannot mark legacy tracks for deletion if rail tracks are chosen for the whitelist filter.
Maybe having a separate entity for them would be better so it can only deconstruct legacy tracks and keep the new ones.
Re: Deconstruction planner cannot mark legacy tracks
Posted: Mon Oct 21, 2024 9:06 pm
by boskid
For a workaround you can import this deconstruction planner which is configured to 1.1.x rails only. I can ask if it would be ok to make rail item in deconstruction planner to also cover 1.1.x rails by default.
Re: Deconstruction planner cannot mark legacy tracks
Posted: Mon Oct 21, 2024 10:20 pm
by ElderAxe
Nice idea. Thanks for the blueprint.
Re: Deconstruction planner cannot mark legacy tracks
Posted: Mon Oct 21, 2024 10:22 pm
by robot256
If the goal is for everyone to tear up their legacy rails and replace them with new, a working deconstruction planner would certainly help
Re: Deconstruction planner cannot mark legacy tracks
Posted: Tue Oct 22, 2024 11:53 am
by boskid
Thanks for the report. In 2.0.9 using deconstruction planner configured for straight-rail will correctly mark legacy rails for deconstruction.
-- edit: On top of that, deconstruction planner from earlier will still work and will select only legacy rails.
Re: Deconstruction planner cannot mark legacy tracks
Posted: Tue Oct 22, 2024 8:50 pm
by Conventia
Thanks, though I think it would be useful to allow people to naturally select the legacy rails since that would allow them to replace their network with only new rails. I have a save with ~100k rails, there's no way I would ever replace them without a way of distinguishing between them.
That said, I can use this blueprint, as long as I never lose it.