[2.0.15] Deconstruction planner don't select chests.

Bugs that are actually features.
TheCherry
Burner Inserter
Burner Inserter
Posts: 11
Joined: Fri Jan 18, 2019 10:00 am
Contact:

[2.0.15] Deconstruction planner don't select chests.

Post by TheCherry »

We are not able to select chests with the deconstruction planer on our savegame.
Nor the Cut tool. The cut tool copy it, but don't remove that chests.
11-12-2024, 11-49-00.png
11-12-2024, 11-49-00.png (647.3 KiB) Viewed 164 times
11-12-2024, 11-49-33.png
11-12-2024, 11-49-33.png (717.49 KiB) Viewed 164 times
Even replace a chest with a another (in this example a wood with a iron chest) don't work.
11-12-2024, 11-50-29.png
11-12-2024, 11-50-29.png (65.2 KiB) Viewed 164 times

In a new game works everything fine. We had 3 mods installed, but even uninstall them, it's don't work.
The mods are: Auto Ghot Builder, Blueprint Sandboxes, Construction Planner Continued


Savefile:
nightraiders2.zip
(13.11 MiB) Downloaded 12 times
Logs (nothing special)::
factorio-current.log
(7.51 KiB) Downloaded 9 times
TheCherry
Burner Inserter
Burner Inserter
Posts: 11
Joined: Fri Jan 18, 2019 10:00 am
Contact:

Re: [2.0.15] Deconstruction planner don't select chests.

Post by TheCherry »

OK I found the issue, we play with the PVP Setting "Neutral chests" that cause that the chests aren't selectable. Is this intended? I don't like that behavior.
Any Idea how to temporary disable this setting and can you include neutral buildings for the deconstruction planner?
User avatar
Lou
Factorio Staff
Factorio Staff
Posts: 181
Joined: Mon Nov 30, 2020 10:50 am
Contact:

Re: [2.0.15] Deconstruction planner don't select chests.

Post by Lou »

Hello. Any regular entities can be deconstructed only by their forces, so the deconstruct, cut and superforce cases are a no-go. There can be a design conversation about blueprintability of enemy and neutral entities, however it is definitely Not a bug -> moving this to not a bug, feel free to start a topic in Ideas and suggestions if you really think some changes about this behaviour should be done.
Post Reply

Return to “Not a bug”