List of 107 words

[Galger]

Hi

Ingame of Elite Dangerous there is a "commodities market". It has 107 commodities and 15 categories. By now i managed to control the first three categories by "When I say" the name of the category. I can go up and down and always see the name of the category.

(How can i post a command?). I made a screenshot of the first two commands. At the end of the month i maybe have those 15 categories  But how do i manage those 107 commodities. Do i really have to create 107 commands for each single one? That would take me forever 

First Category
2 commodities

Second
27Category

Third Category
3 commodities

And so on

[Pfeil]

If the commands can be split into two parts, you can use prefix/suffix to manage them.

The way I do this is to treat the suffix like a database lookup, in a sense; The prefix does most of the logic, while the suffix provides the data.

This is accomplished by using jumping into the suffix to read the required data, then jumping back into the prefix to do something with that data:
(Prefix) "Is there data on "

Code: [Select]

Jump to Marker: SetType
Marker: TypeSet
Begin Boolean Compare : [~~data] Equals True
    Write '[Blue] There is data' to log
Else
    Write '[Blue] There is no data' to log
End Condition
Exit Command
Note the "Exit Command" action, which prevents execution from going back into the suffix and causing a loop.

(Suffix) "something"

Code: [Select]

Marker: SetType
Set Boolean [~~data] to True
Jump to Marker: TypeSet

You can pass any number of variables. I find it's best to work out which data you need to store/process, and set up a template you can duplicate.

If you want to speak the subject in the suffix instead, it becomes much simpler, as you don't need to jump back and forth at all(set data in the prefix, process in the suffix), but I find it's more natural to speak the operation before the subject(E.G. "what is lettuce" rather than "lettuce, what is it") in most situations.


Logically, this is the equivalent of a long conditional chain, but UI-wise it makes managing and adding values less of a hassle.

If subroutines are implemented, this sort of thing could be managed that way instead, but currently I believe this is a reasonable balance between functionality and complexity.


If you really want to make it complex, you could store your values as a list or even in an actual database, and dynamically build a "when I say" phrase for a command that looks up the relevant data at the time of execution instead, but then editing the data could become cumbersome.

[Galger]

Thank you for the answer but i just found out that not every commodity market offers the same commodities. I dont know if it will still work?

[Pfeil]

Ah. I inferred you wanted to query static information rather than control an ingame interface.

For what you're looking to do, you'd need a data source that can tell you what's available at your current location specifically.

There appear to be many options available, I don't play E:D so I don't have any insight as to which works best.

E.G.
Elite: Dangerous Market Connector (EDMC) seems to provide data that may be of use.