No Deconstruction Timeout

[Rseding91]

I mark something for deconstruction, because I want it to be deconstructed. I think, it adds to confusion, if the game decides, that the order was not important after 2 hours and removes it (probably without notice). If you work on a big project like solar, 2 hours might be short. Importance is not necessarily the same as urgency.

I get, if there are technical limitations or performance issues or simply a game design decision, other that I see no big benefit for the expiration.

It's performance related. The more orders you have outstanding that aren't being worked on the slower it is for the logic to get around to ones it can work on. So if after 2 hours you still haven't provided something to work on the order it assumes you aren't ever going to and cancels the order.

[adam_bise]

For me it was a situation where I have a 20 minute train ride between my mall and my new site. The blueprint for the site is large, and I don't even know how many biter nests I will need to clear until I place it on the map. Then I have to actually kill the biter nest, go back and gather up all of the ingredients, which might take a while to get 12kbelts, 14k rails etc all loaded up and back to the site.

By the time the decon timeout happens I have already built power and made modifications to the ghosts. So re-stamping the BP becomes a pain in the ***

I'd just rather handle cancelling my own orders then being surprised or trying to hurry.

Here's an example of why it might take me a while. Even though here I will re-stamp it before gathering the supplies since the biter nests will block the ghosts and part of the map isnt even revealed yet.

0.png (111.43 KiB) Viewed 2042 times

[jodokus31]

I mark something for deconstruction, because I want it to be deconstructed. I think, it adds to confusion, if the game decides, that the order was not important after 2 hours and removes it (probably without notice). If you work on a big project like solar, 2 hours might be short. Importance is not necessarily the same as urgency.

I get, if there are technical limitations or performance issues or simply a game design decision, other that I see no big benefit for the expiration.

It's performance related. The more orders you have outstanding that aren't being worked on the slower it is for the logic to get around to ones it can work on. So if after 2 hours you still haven't provided something to work on the order it assumes you aren't ever going to and cancels the order.

Yeah, that's completely understandable. The amounts of orders can get really big really fast and if they last forever, it grows and grows. After all, it's a game which has to be processed on a CPU and limited memory and not real life, where are no such limitations.

*snip*

It's probably better to make smaller blueprints, or multiple, which also help to prioritize important things, like power and defense. Or does your mod help?

[adam_bise]

It's probably better to make smaller blueprints, or multiple, which also help to prioritize important things, like power and defense. Or does your mod help?

Yes! It works just fine. I've been using since. Thanks for your help with it!

[Qon]

Mind if I ask: why? The default is 2 hours but if you've marked something for deconstruction and over 2 hours later you still haven't gotten around to letting a robot work on it why is it important? Obviously it wasn't important since 2 hours has passed and it still wasn't handled.

I'm making a self-building factory. I'm probably not going to run into the 2 hour limit since I'm designing around the limitations. But it would be nice to know that the build commands I run were followed always eventually instead of probabilisticly sometimes. Why are robot jobs outside construction networks even in the queue? The ghosts (and deconstructions) could be just stored on the chunk only and use no CPU time until the addition of new or moved construction network area would search for ghosts and add them to the queue. So when a roboport is placed or powered on it activates (add to queue) the inactive ghosts within its own reach. And by ghosts I mean deconstruction orders as well.

This way I could place a blueprint that takes 1000h to build (some of the time would be waiting for things to be crafted) and wait for the bots to do it with no performance penalty (or bot activation delay) for ghosts that are outside any construction network.

[hackamod]

it would be nice to know that the build commands I run were followed always eventually instead of probabilisticly sometimes.

+1

Checkbox in the options to disable this?

[Nidan]

I mark something for deconstruction, because I want it to be deconstructed. I think, it adds to confusion, if the game decides, that the order was not important after 2 hours and removes it (probably without notice). If you work on a big project like solar, 2 hours might be short. Importance is not necessarily the same as urgency.

I get, if there are technical limitations or performance issues or simply a game design decision, other that I see no big benefit for the expiration.

It's performance related. The more orders you have outstanding that aren't being worked on the slower it is for the logic to get around to ones it can work on. So if after 2 hours you still haven't provided something to work on the order it assumes you aren't ever going to and cancels the order.

Is there a chance to revisit this for SA, considering the improvements from FFF 415?
I ran into this while setting things up on Gleba. I went through the initial unlocks, so I could design science and rocket production with machines that have their recipes set. While doing that there were issues forcing me to return to Nauvis and then stayed there, while continuing the design on Gleba via remote view, using the landing pads free radar coverage as I have no automatic energy production yet. At some point I had to move some of the stuff I had already built while on Gleba, to make room for other buildings. Cue me being confused the next day, after I found the new buildings' blueprints suddenly missing (due to the colliding deconstruction orders expiring).

[BraveCaperCat]

I mark something for deconstruction, because I want it to be deconstructed. I think, it adds to confusion, if the game decides, that the order was not important after 2 hours and removes it (probably without notice). If you work on a big project like solar, 2 hours might be short. Importance is not necessarily the same as urgency.

I get, if there are technical limitations or performance issues or simply a game design decision, other that I see no big benefit for the expiration.

It's performance related. The more orders you have outstanding that aren't being worked on the slower it is for the logic to get around to ones it can work on. So if after 2 hours you still haven't provided something to work on the order it assumes you aren't ever going to and cancels the order.

Is there a chance to revisit this for SA, considering the improvements from FFF 415?
I ran into this while setting things up on Gleba. I went through the initial unlocks, so I could design science and rocket production with machines that have their recipes set. While doing that there were issues forcing me to return to Nauvis and then stayed there, while continuing the design on Gleba via remote view, using the landing pads free radar coverage as I have no automatic energy production yet. At some point I had to move some of the stuff I had already built while on Gleba, to make room for other buildings. Cue me being confused the next day, after I found the new buildings' blueprints suddenly missing.

This is a separate issue, as "Time To Live" for ghosts has been removed in 2.0 and replaced with "Create Ghosts when destroyed".

[Nidan]

I mark something for deconstruction, because I want it to be deconstructed. I think, it adds to confusion, if the game decides, that the order was not important after 2 hours and removes it (probably without notice). If you work on a big project like solar, 2 hours might be short. Importance is not necessarily the same as urgency.

I get, if there are technical limitations or performance issues or simply a game design decision, other that I see no big benefit for the expiration.

It's performance related. The more orders you have outstanding that aren't being worked on the slower it is for the logic to get around to ones it can work on. So if after 2 hours you still haven't provided something to work on the order it assumes you aren't ever going to and cancels the order.

Is there a chance to revisit this for SA, considering the improvements from FFF 415?
I ran into this while setting things up on Gleba. I went through the initial unlocks, so I could design science and rocket production with machines that have their recipes set. While doing that there were issues forcing me to return to Nauvis and then stayed there, while continuing the design on Gleba via remote view, using the landing pads free radar coverage as I have no automatic energy production yet. At some point I had to move some of the stuff I had already built while on Gleba, to make room for other buildings. Cue me being confused the next day, after I found the new buildings' blueprints suddenly missing.

This is a separate issue, as "Time To Live" for ghosts has been removed in 2.0 and replaced with "Create Ghosts when destroyed".

No. Maybe I could have made the last sentence clearer, but the cause for the ghosts vanishing was that the buildings they were colliding with were no longer marked for deconstruction. (Also, didn't ghosts already have practically infinite live in 1.1?)

[BraveCaperCat]

I mark something for deconstruction, because I want it to be deconstructed. I think, it adds to confusion, if the game decides, that the order was not important after 2 hours and removes it (probably without notice). If you work on a big project like solar, 2 hours might be short. Importance is not necessarily the same as urgency.

I get, if there are technical limitations or performance issues or simply a game design decision, other that I see no big benefit for the expiration.

It's performance related. The more orders you have outstanding that aren't being worked on the slower it is for the logic to get around to ones it can work on. So if after 2 hours you still haven't provided something to work on the order it assumes you aren't ever going to and cancels the order.

Is there a chance to revisit this for SA, considering the improvements from FFF 415?
I ran into this while setting things up on Gleba. I went through the initial unlocks, so I could design science and rocket production with machines that have their recipes set. While doing that there were issues forcing me to return to Nauvis and then stayed there, while continuing the design on Gleba via remote view, using the landing pads free radar coverage as I have no automatic energy production yet. At some point I had to move some of the stuff I had already built while on Gleba, to make room for other buildings. Cue me being confused the next day, after I found the new buildings' blueprints suddenly missing.

This is a separate issue, as "Time To Live" for ghosts has been removed in 2.0 and replaced with "Create Ghosts when destroyed".

No. Maybe I could have made the last sentence clearer, but the cause for the ghosts vanishing was that the buildings they were colliding with were no longer marked for deconstruction. (Also, didn't ghosts already have practically infinite live in 1.1?)

About 50+ hours in 1.1.