AlexSatrapa
commented
2 months ago Good place to start is reworking power, moving power to a resource group within the structure database, rather than being uniquely an attribute of structures.
Next question is whether to incorporate the recipes into the same database as the structures, or keep them separate. Structures in column A, resources in column B?
example:
- name: Animal Husbandry Facility
materials:
Adaptive Frame: 5
Aluminum: 8
Reactive Gauge: 3
Sealant: 3
structure:
cargo: 0
power: -3
recipes:
- name: membrane
- water: -1
- fiber: -1
- power: -3
- membrane: 1
- name: analgesic
- water: -1
- fiber: -1
- power: -3
- analgesic: 1
type: builder
And all those numbers will need to be determined. I can see the need to include character skills and crew skills at some point in the future, so these numbers will all need to be relative to something and normalised against that references.
Kestrel's Outpost Spreadsheet has some stuff about demand/supply so you know what you need to bring into a particular outpost and what it can produce.
I'd imagine this working something along the lines of an extra block of output similar to power check.
A simple example:
Wind Turbine is a producer, it produces 25 power (as defined by the label as part of power-check logic).
Animal Husbandry Facility is a producer, but also a consumer. Depending on the recipe it needs fiber and water. How do we tell? I'll have to build a list, or assume fiber unless the label is notated like (analgesic: stuff). So keep track of demand and supply:
The net output of this should be that this outpost requires an import of antimicrobial.
So guess I need to add production and consumption numbers to each outpost structure, and then build a list of recipes for each fabrication structure (pharmaceutical lab, extractor, greenhouse, animal husbandry facility, fabricator).
Abuse of labels continues:
But the hard part will be the database.