What about this: the ability to Export map, then a dialogue to select what ELSE get's exported? Objects, VBL, tokens, etc. You could even allow for a fine-grained selection (save token X, but none of the rest) via tree-style checklists (or whatever those are called). And you could have the same dialogue show up on import.DrVesuvius wrote:Seconding right back atchya. For me "Saving A Map" means the pretty stuff that I move my tokens around on top of. So that would be Background and Object layer, drawings and stamps. Oh and VBL I guess (though I don't personally use that). No tokens, campaign properties, states or anything like that.
I can understand how some users might think of saving a map as saving a pre-packaged encounter, with populated monster tokens already set up ready to pounce. That's a perfectly valid user requirement too, and I can see how that would be harder to implement.
"Save Current Map" vs "Export Current Map as Campaign/Import Campaign" - two different sets of functions.
If the first one is achievable it'll be useful for some of us.
Even if "Save Current Map" couldn't save VBL, it would still be a time saver (it being quicker to add VBL to an already drawn map than to draw the map from scratch, and THEN still have to add VBL manually.
This way, if you are exporting for personal use, you only transfer what's necessary, but if you are transferring for community use, then you can give more, and let the end-user select what they do and do not want, down to the bare map if they so desire. All with a few mouse clicks, as I see it.