[2.1.9] Vehicle inventory logistical request dont reset on enemy team breaking them
Posted: Mon Jul 06, 2026 5:32 pm
What did you do?
I set up an item-voiding system on Fulgora using a biter to destroy cars:
A captive biter is placed between two cars.
The biter continuously attacks and destroys both cars.
Recyclers processing scrap feed items directly into the cars, which fills their fuel slots with solid fuel (50 units).
The cars are covered by a roboport network with construction bots and are rebuilt from ghosts each time they are destroyed.
What happened?
When a car with a full fuel slot is destroyed, its ghost retains the 50 solid fuel as an item request in the fuel slot. Upon rebuild, logistic robots attempt to fulfill that request, but the adjacent recyclers instantly fill the slot first. However, the logistic request is not cleared when the slot is filled by the recyclers.
Over time, the pending logistic request grows to very large numbers — far beyond the logical 50-item capacity of the fuel slot — as if every destroyed car instance were still contributing its own 50-item request cumulatively, instead of the request being cancelled or replaced when the entity is rebuilt and its slot filled.
What did you expect to happen instead?
I expected the item request to be capped at the fuel slot capacity (50 solid fuel), and to be cleared once the slot is filled by any source (in this case, the recyclers). Requests from previously destroyed instances of the car should not accumulate.
Does it happen always, once, or sometimes?
Always. The request value grows continuously as long as the destroy/rebuild cycle keeps running.
Steps to reproduce:
Place a car and fill its fuel slot with 50 solid fuel.
Place a biter (or any damage source) that repeatedly destroys the car.
Cover the area with a roboport network with construction bots and materials so the car is rebuilt each time.
Have recyclers (processing scrap) inserting solid fuel into the car so the fuel slot refills instantly on rebuild.
Observe the car's logistic requests after several destroy/rebuild cycles: the requested amount keeps increasing well beyond 50.
I set up an item-voiding system on Fulgora using a biter to destroy cars:
A captive biter is placed between two cars.
The biter continuously attacks and destroys both cars.
Recyclers processing scrap feed items directly into the cars, which fills their fuel slots with solid fuel (50 units).
The cars are covered by a roboport network with construction bots and are rebuilt from ghosts each time they are destroyed.
What happened?
When a car with a full fuel slot is destroyed, its ghost retains the 50 solid fuel as an item request in the fuel slot. Upon rebuild, logistic robots attempt to fulfill that request, but the adjacent recyclers instantly fill the slot first. However, the logistic request is not cleared when the slot is filled by the recyclers.
Over time, the pending logistic request grows to very large numbers — far beyond the logical 50-item capacity of the fuel slot — as if every destroyed car instance were still contributing its own 50-item request cumulatively, instead of the request being cancelled or replaced when the entity is rebuilt and its slot filled.
What did you expect to happen instead?
I expected the item request to be capped at the fuel slot capacity (50 solid fuel), and to be cleared once the slot is filled by any source (in this case, the recyclers). Requests from previously destroyed instances of the car should not accumulate.
Does it happen always, once, or sometimes?
Always. The request value grows continuously as long as the destroy/rebuild cycle keeps running.
Steps to reproduce:
Place a car and fill its fuel slot with 50 solid fuel.
Place a biter (or any damage source) that repeatedly destroys the car.
Cover the area with a roboport network with construction bots and materials so the car is rebuilt each time.
Have recyclers (processing scrap) inserting solid fuel into the car so the fuel slot refills instantly on rebuild.
Observe the car's logistic requests after several destroy/rebuild cycles: the requested amount keeps increasing well beyond 50.