Personal flags left on locations are not present after disconnecting and reconnecting.

Flags definitely do not have a GUID, which means they are going to have to be treated specially.

This will require a protocol break, which I'd rather not do for 0.1.3.1, so I'm bumping this back to 0.1.4.0

After further testing, flags do actually have a GUID, sometimes...

You need to leave the flight (Packing and unloading is not enough), and then load back in for flags to get saved on the server. It's pretty horrid and I can't understand why KSP does this, but DMP tracks vessels by GUID. No GUID means we can't track the vessel properly.

This may still be possible if we track flags by the root part ID - But only if it's constant.

Slightly dodgy, but fixed in ecc497a

Flags appear to have an empty GUID - I'll likely have to store them in a special folder.