What?
Some improvement of item request, for example:1. don't cancel remote item request when change entity quality. (or allow control whether cancel)
2. blueprint remote item request (or allow control of them)
Why?
Remotely put item ghost inside entities are a great feature, but they behave a lot inconsistently. I've noticed some tricky situations that it's default behaviour is causing trouble.Now requests in ghosts are blueprinted, but in actual entities are not blueprinted. This is a useful QoL most of the time, but sometimes we frequently need the reverse, so generally a lack of control problem.
Example: I'm making some bootstrap blueprint, like fluoroketone barrel request inside assembler, rocket fuel request inside heating tower, fussion fuel request inside fussion reactor, onc-time raw material / ammo request for space platform quick startup. But whenever I want to update this blueprint, I need to make a new set of ghost entities instead of blueprint my current built and tested entities.
I think just retain all request is not a good idea either, that's why it's not the default behaviour. A good and simple solution would be just always blueprint them,
add a catergory as "item requests" like train fuels. So when I don't need them I can easily turn them off. When not blueprinting, retain current behaviour. So when I need it I actively blueprint it which is not a lot of effort.
Speaking of train fules category. Item requests in blueprint are somewhat badly displayed. I'm not clear the full mechanics, but I guess now only fuels display on the left side of blueprint, other item requests do exist but not showing up. So I can see carbon (for explosives, actually not fuel), but not see iron ore.
And I also want blueprint allow(on/off switch) ghosts with empty modules can retain entities' module when pasted, currently a empty moduled machine blueprint would remove all module from a machine. So when I update a machine's setting or bootstrapping from a blueprint, It doesn't suit all module setups, and need I update/make a version for each module. I will post this as a seperate suggestion, just mention it as related here.