[2.0.33] Bot stuck in mid air after deconstruction
Posted: Fri Jan 31, 2025 3:24 am
What did you do?
Attempted to deconstruct a beacon in remote view.
What happened?
A construction bot came to perform the order as normal, but then the bot got stuck, throwing up an out of storage alert even though the network it was in should have had storage available. I checked to make sure the network it was in was not accidentally isolated or disconnected, then tried placing a new storage chest nearby, as well as another roboport. None of these actions were able to resolve the issue. (see attached images)
I also did a keyword search just in case and found this report where it was marked as not a bug because turned out that the stuck bots belonged to a spidertron: viewtopic.php?p=653584, but I did not have any spidertrons near the location so I do not believe that was the cause of the issue.
What did you expect to happen instead? It might be obvious to you, but do it anyway!
That the bot would be able to complete its task as normal, deliver the beacon + modules to storage and then return to a roboport.
Does it happen always, once, or sometimes?
Only the one time I've had this issue occur.
Attempted to deconstruct a beacon in remote view.
What happened?
A construction bot came to perform the order as normal, but then the bot got stuck, throwing up an out of storage alert even though the network it was in should have had storage available. I checked to make sure the network it was in was not accidentally isolated or disconnected, then tried placing a new storage chest nearby, as well as another roboport. None of these actions were able to resolve the issue. (see attached images)
I also did a keyword search just in case and found this report where it was marked as not a bug because turned out that the stuck bots belonged to a spidertron: viewtopic.php?p=653584, but I did not have any spidertrons near the location so I do not believe that was the cause of the issue.
What did you expect to happen instead? It might be obvious to you, but do it anyway!
That the bot would be able to complete its task as normal, deliver the beacon + modules to storage and then return to a roboport.
Does it happen always, once, or sometimes?
Only the one time I've had this issue occur.