+each structure has one input per item and one output per item (not stored directly, stored by saving 'recipe:<recipe name>')
+each structure has a 'sprite' (pointer to an array of ntca's for printing) (stored in the 'sprite:<name>' entry in the json saves )
+each structure has an id (stored in the 'structure:<name>' entry in the json saves)
+connections are 'lengthless', only including a maximum throughput, an input, and an output (exactly one of each per connection) branching must be done by dedicated structures (stored as 'connection{throughput:<number>, input:<UID of feeding structure>, output:<UID of fed structure>}')
+connections are 'lengthless', only including a maximum throughput, an input, and an output (exactly one of each per connection) branching must be done by dedicated structures (stored as 'connection{throughput:<number>, input:<UID of feeding structure>, output:<UID of fed structure>}')
item design ideas:
+item stack sizes are unlimited (as far an uint_N is concerned), but structures may impose their own limits on stack size
+stored as 'item:{id:<item name>, count:<count>}'design documents, yum yum
