dataHandler tick count

[Sauron754]

the data handler will need to be able to save tick count somewhere

[Sauron754]

also would be helpful to add a start file writing/filling pattern to all new... functions; what I mean is a default set of variables/lines which are automatically written to the save and then just need to be modified

[taragor]

you can save the tick count in current.universe (can save a theoretical unlimited number of parameters) i can add some start parameters, just give me a list

[Sauron754]

okay I would say we have another parser, which handles the low end stuff so that when we actually need to work with saves we can just say -> give me this parameter and then he finds out which line to check and returns the parameter

list of usefull parameters

• object position(as we are doing it iteratively and not tick wise) / probably the easiest way ist to save whole objects and then we can access all of their data
• eventual craft files
• eventual flight plans
• maybe setings

predefined we might want to have segments (like a data structure) e.g.:

objects{ (brackets open the part where objects are saved) object name[ property1; property2; etc. ] } (again bracket for closing the objects part) and then the same for crafts and flight plans

as default lines we should write the segments (like objects, crafts, flight plans) and then into the objects add a "starting solar system"

[Sauron754]

should I take over this job because i think you have enough to do with the simulation?