Steps to reproduce :
Setup :
- create a logistic request on a space platform hub. Set a non default surface (IE : create a request for stones, imported from Vulcanus, or tungsten from Gleba)
- give it a name (to create a global requests group)
- put a requester chest somewhere / use the surface landing pad (bug is present for each)
- attribute it the same requests group name
Bug :
- in the chest / landing pad setup window, open the request in the requests group (ie stones from Vulcanus) (click on the icon to adjust the request)
- validate it with the green tick
- go to the space platform hub
What should you see ?
- the surface filter of the request of the request group has not changed (nor any other parameters)
What I see :
- the request in the request group is now attributed to the default surface for the ingredient (even if the requester chest is somewhere else)
- the custom payload setting has been reset
Reproductibility : 100 % wherever the chest or the requests group UI as long as it's not the space platform.
Screenshot and more details available on demand. Save file provided with stones from Vulcanus, in a requests group called "'Depuis Vulcanus" on platform "Voyager Vulcanus" (yes, it's a real use case)
[2.0.21] Surface filter not kept in logistic requests groups
[2.0.21] Surface filter not kept in logistic requests groups
- Attachments
-
- SA octobre 2024 [entity=cargo-pod] Fulgora.zip
- (19.2 MiB) Downloaded 11 times