Deconstruction planner cannot mark legacy tracks

[ElderAxe]

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.

[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.

0eNqdj0EKgzAQRe8yawW1Kij0JKVISKY2kExsHKUiuXtHShftsquEx58HbweDOtDMcdFsAw2TU0QYod9hRmZL43z8kdjyNtysY4xCLjuQ8gg9OByV3nIxKDveOZfHQQaPRTm5kAGF6NWBdPCTioqD2OEswJLBJ/RFyn5teokrmj9cZbpmwNbhMKPDd5IPRtRVkhGjl/13cv5JzmCVNiHQN23V1V3XnLq6aYsypRcyS2Zc

Copy blueprint

[ElderAxe]

Nice idea. Thanks for the blueprint.

[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

[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.

[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.