Can we have a function to erase (not clear) the internal file ?
-
If we want to preserve peoples data (for example highscores) generated by a program in the file system it seems we must share without the internal file present and when doing updates also make sure the file is not present (does not exsit). @vinicity seems to have tested this already. What people currently do is copy code / assets / levels / recreate bookmarks in a new project to make sure the file does not exists before sharing or updateing / resharing but this seems very tedious and i'm not even sure the download ID would remain the same when doing this.
So would it be possible to add a function inside fuze that we can call from within the code to erase (not clear) the data file present in a project to prevent all this hassle ? This way before sharing we can call the function in the beginning of the program, and put an endless loop / update / repeat call behind it run the code (file would be erased) and then we erase the function call and that endless loop and the game would be in a state as when we had never run the game before without the internal file present and it would not overwrite the file when people update to a new version of our projects
This seems to me a lot less of an hassle than what we currently have to do to prevent updated / (re)shared versions of a project overwriting data (for example highscores) with users having a previous version already installed (with such file already existing from running the project).
the reason i would suggest this using a function call is so we (programmer of project) can control it and people don't accidently erase the file in some project if fuze got some general option for it inside fuze itself. As such data file can contain critical data as well necassary for the project to run and not just saved options / highscores
-
Thank you both for the stimulating discussion. To clarify something here - I did not say that the team are "thinking about implementing a proper file system". I said that the file system functionality will likely see some improvements in the future.
While I won't go into too much detail here, there are more considerations than just what Nintendo may or may not let us do. That certainly is one, yes. But we are still a very small team currently, and we cannot do it all at once. Patience here is much appreciated.
