Page 1 of 1

[2.0.34] Super-force upgrading into logistical chest loses its control behaviour

Posted: Wed Feb 12, 2025 7:40 pm
by Hares
Steps to Reproduce
  1. Deploy logistical chest of any kind (active provider, passive provider, storage, buffer, or requester)
  2. Configure its "Enable/disable" condition
  3. Copy it via Ctrl+C
  4. Super-force deploy it over existing non-logistical chest (i.e., steel chest)
Expected:
  • New chest is deployed via deconstruction/reconstruction (2.0 limitation of upgrade tasks not having full set of properties)
  • New chest has same "Enable/disable" condition as source
Actual:
  • New chest is deployed via upgrade task
  • New chest has no "Enable/disable" condition
See Also
Click to expand the recording - One chest - Detailed
Click to expand the recording - Five chests - Fast
Hi, Lou! Sorry, it's me again.

Re: [2.0.34] Super-force upgrading into logistical chest loses its control behaviour

Posted: Mon Apr 21, 2025 11:04 pm
by Rseding91
Thanks for the report however I do not believe we will be doing anything about this.