Parameterization of Logistics Groups

[macintacos]

I was in the middle of trying to make generic space platforms, and ran into a variety of limitations related to parameterization. The one that I want to discuss here is related to parameters in logistics groups and the logistics groups _names_.

I want to be able to logistics group set as something something like this:

01-01-2025, 16-32-39.png (40.75 KiB) Viewed 329 times

Where:

- Param 0 is the item I want to request
- Param 1 and 2 are the source/destination planets

These parameters would also be used elsewhere in combinators on the ship that get build from the blueprint. The way I'd imagine this working is, if a logistics group exists that matches the values that are provided in params 0, 1, and 2, it would use that existing logistics group - otherwise, a new logistics group would be created with the naming provided.

The way I'm trying to use them at least, this would really help with setting up generic "haulers" that go between planets. The way I set up the schedules, they have a set of requests that are common among all haulers (magazines, walls, repair packs, etc.) and then have one or two items that the platform will be "hauling" between planets. If I were able to parameterize logistics groups, this would simplify the setup of these haulers a bit. Hope that makes sense!

[Muche]

Interesting.

I tried it, and it seems using a parameter in a logistics group name invalidates that group from further parameter-related processing.

[Muche]

Also see 125477 Signals in constant combinator with description not parametrizable.