ApplicationStorageDirectory - Best Practice for Games Question
So I've been working on a game which uses AIR. My problem is that I have been storing my game assets in the application directory. That would be fine except that the game has a built-in editor which requires the ability to write files. Adobe has since locked the ApplicationDirectory to write access, so now I'm not sure of where I'm expected to store all of my user editable game files - which is potentially ALL game assets.
The seemingly obvious choice is to use ApplicationStorageDirectory. While not ideal, in that it seems I would need to duplicate all assets from inside the application to the storage directory on startup, it would provide a standard and easy to find place to store editable game assets.
However, this article (on this site) clearly tells me that I should not do that. It makes a good point. Backing up all of the games assets is messy proposition. And while I can see users who take advantage of the editting capabilities as appreciating the backup, for the average player, that would be a pretty big annoyance.
So what am I expected to do in this scenario? I need a writable location where the user and the application can easily access all game assets ( XML, Image, MP3 ). I don't want to pick an arbitrary location, and I'm turned off by the application needing to redundantly house the data just to copy to the destination directory since there's no way for me to delete it once it's copied since I can't write to the application folder.
Thanks for the thoughts.