Hierarchical variable access

Feedback
,
1

The new screen variables add a lot of functionality, but there is a gap. Specifically I’m thinking about commands that are based on a base, but don’t use the planet id as the variable. For instance the WF, PROD, EXP commands share an ID, that I’m guessing is for the base, but the BS command uses the planet ID. If we could use some sort of dot notation to access these variables we could build better screens. Like, PROD %PlanetId%.BaseId. Same for inventories. Each inventory has a unique id, but it would be nice if we could access those values from a base or planet id, i.e. INV %PlanetId%.BaseStorage and %PlanetId%.WarehouseStorage.

There may be a better syntax, or even a way to make the derived variables explorable in the screen variable setup. However it’s accomplished, being able to derive related Ids would be nice.

2 Likes
2

I am pretty sure that there was already another post with this topic but I can’t find it so I guess it was on another platform.

Agreed, without access to the inventory screens the usefulness of these variables is limited. They still work for shopping though.

3

I think the discussion was under Molp’s note about the new commands - and we noted the commands it doesn’t work with (I think BRA is also a problem) - I don’t think it was a separate topic.

4

Nevermind - “Redefine Commands to always accept planet ID” - last comment 29 days ago. In Feedback.

5

Oh, yea. That’s a better option. I just figured out a better method than the dot notation syntax, but just having the option for a Planet ID for all relevant commands is quicker and easier.