I have another legal concern related to MV. Perhaps more specific is that I ran into an issue where a host app that I built to support Xbox deployment has the unfortunate limitation of not being able to read an LZString when saving files - only the raw JSON code is visible to my WinRT interface (and the base64 compression used by the default save method has no effect on this). So my implementation has to use the "behind the scenes" version instead, because in a browser-based app the storage is not saved on the local disk but in the browser cache. And needless to say, I require a hybrid save solution to accommodate this properly such that a missing disk file affects its matching file in the browser cache. (Or in other words, if you accidentally move or delete the file while not in the game, then its pair is deleted from the browser cache on the next launch.)
Obviously this is useful for things like cloud backup which is my primary reason for doing so (I mean, who the hell wants to redo their entire game because of a device failure?) but at the same time I don't want to go too far with this.
Obviously this is useful for things like cloud backup which is my primary reason for doing so (I mean, who the hell wants to redo their entire game because of a device failure?) but at the same time I don't want to go too far with this.