Estimating save file size...

[TangentFoxy]

It seems like I'm aiming for 75k systems per galaxy (and let's stick to one galaxy for now!). At a minimum, a player who has visited all systems needs to store a value for how long it's been since they visited a system. If I am using a human readable save format, and these use a timestamp, they'll take 10 bytes each. Purchased map data has a similar purpose and needs a date assigned.

• Clearly, I should use days or weeks instead, and consider making the save format binary.
• Instead of storing multiple values that combine to equal a value for how effective transit to a system is, I should just use a single familiarly value? Eh. Doesn't quite work with my ideas, but isn't terrible..

An economy effect via player interaction or universe simulation should be stored. This needs to store at least a handful of things.

It's important to note that most of the galaxy is uninhabited. These values don't exist in many places.

[TangentFoxy]

See #19 (save handling libraries)