Mapping Saving and Merging data best practices

Post Reply
davidwiththenicehat
Posts: 23
Joined: Tue Jul 02, 2019 4:29 pm

Mapping Saving and Merging data best practices

Post by davidwiththenicehat »

Thanks for reading.

Am I understanding correctly that the generic mapper does saves player location with table map.save[charactername]? Then saving the table map.save with table.save? I was wondering if saving to userData would work than thought that pushing out a new map database would clear the character location.
Is writing map data to a table.save still be considered best practice?

Somewhat on subject with the last question.
I would like to support multiple people mapping. Sharing the map data they collect. Than if possible support offering that data to other clients.
I am looking at generic mapper functions map.import_area and map.export_area as a guide.
Using the same general method than exporting to json, to offer support for other clients.
Everything seemed strait forward. Though I feel confident I misunderstood function map.fix_portals. It looks like it converts userData entries to special exits. I know it is needed. I could not figure out why. It looks like special exits get exported and imported. Why store exits as userData?

Thanks for your time!

Post Reply