Before rolling out this change, would you consider implementing Tools to help player transit to that update? With this new constraint, we will need to dismantles constructs, and/or merge constructs that were on separate cores - because of older contraints (like the parenting before it was fixed). It is a lot of boring work, for no plus value for the players (other than conforming to Panacea). You can help make that transition less painfull by:
- Add tools to disassemble a construct in the current container, instead of removing everything 1 by 1
- Increase the copy-paste volume size if possible
- Enable copy-paste of elements
- A tool to offset everything in the building zone
- A way to align constructs, especially when using blueprints
- Would you consider a tool to "upgrade" i.e. replace a core with a larger one?
- Would you consider XL cores or cores with different shapes? A lot of our constructs are just tarmacs, ramps, parking space, voxel libraries, etc. They barely contains elements. Because of the small core, a lot of us endup with a box-style base. We used other smaller cores to build outside the base itself, just for aesthetic - and mitigate the box-like base. With more room, we can still keep the same base, but integrate the aestetic extras inside the same core.
With all these tools, we could rearrange things around, and reduce the core counts (which is the intended goal). Please notice, that a lot of times, we are stuck with a higher core count because of previous game limitations. Example: We created parking space very far away from each other, with multiple core inbetween because of the bad parenting (that is now fixed - thank you).
Yes, deconstruction is incredibly tedious we do need a remove all command like remove all elements and remove all honeycomb that would be a welcome change and it eliminate the need for support to help with lost/buried honeycomb. and it would make deconstruction much faster and less of a burden.
