Files and sharing
-
Hey,
Great app(IDE?), I am in love with it and can't wait to participate in the first competition.♥️
I got a conceptual question: If I
write()to a file, will the file also be shared with the program, or do I need to rewrite it?Essentially: is writing a file intended for save games (no sharing) or is it intended to be used like assets (part of the share?)
-
@mario-bodemann That is a really good question. I think so but I will have to try it to confirm. Unless anyone else would like to confirm this!
-
@mario-bodemann So i have just tried that and the file contents was included in the share
-
Lovely @pianofire,
Thank you for your quick response and trying it out! 👍
-
Really? Surely thats a bug isn't it? If I write a high score save into my game and then share it, I don't want to share my high scores too...
-
I like the idea that the file is shared. Sharing the file would allow creators to use the file for level data, in stead of embedding it in their code for instance...
But it would be nice if there is some way to view what file content you are sharing. just in case you once wrote sensitive information to the file as an experiment,and aren't aware that you're sharing it with a project where you might not even use it.
-
@PB____ thanks for posting the link to this thread. I just took it as "by design" to show default high scores for an example. As you said, it would be nice, if we could see that file in the media afterwards. And maybe show it as a text, to check contents. And if we do not want to share the high scores, we just delete it there.This would be nice feature.
-
Hi all, I just started using Fuze a few days ago, and I must say, I've had a lot of fun so far. I've been accumulating miscellaneous questions as I've been working on my first game (most of which I've been able find the answers for by searching the forum), however, I was searching for an answer for this very question and wanted to post my opinion. To me, the idea that the file is shared seems very unintuitive. My initial thought was to use the file as a place to store configuration settings, high score, etc., and so I would definitely not expect the file to be shared with others. I can see the utility of using the file for game assets (instead of game state), but I can't imagine that is the most common use case. Perhaps it would make sense to be able to open a file as "local" (not shared) or "global" (shared). Additionally, it would be awesome if we could open multiple files (so we don't have to write everything we need to persist into a single file).
Anyways, I just wanted to make my first post and start contributing to the community, and I figured this was as good as a place as any to start :-)
-
...and to add to this discussion, I would like the option to push out an update of a program and somehow choose not to have the user's file overwritten by the update.
That way, save data and high scores can be kept even as the program itself is updated. -
Even though Gothon has created an entire file system in Fuze (https://fuzearena.com/forum/topic/1207/a-persistent-file-system), I do agree that having native support for multiple files per program in Fuze would be really nice.
I'm not sure if it is a good idea to remove the ability to share your files along with your program now.
But in a broader scope, I think it could be nice to have more control about sharing, so you would have the option to configure for individual assets if they should be uploaded (or downloaded) -
It definitely would not be good for me to remove the ability to share the save file. I feel like there’s workarounds for most of this stuff at the moment, and imagine that the savefile functionality may be tweaked or added to in the future. For now though, I’d encourage new users to check out pianofire’s ‘persistent data’ functions (search in the forum for it), and/or gothon’s file system stuff, and/or spikey’s persistent high score table.
