Hi guys.
I have a somewhat weird question i guess. Maybe someone can help me with it.
Currently i fiished building an app for MSFS that allows users to backup and revert, or share control profiles. (Im aware about the cloudsave etc).
Ive made a few apps before but they were in JS and i never thought about it, since they cant really harm a lot.
But this backup app has at least the potential that users using it wrong and overwrite wrong profiles etc.
How can i make sure that this is on their own risk and i cant be made responsible, in case something is off?
Ive build this more or less for myself, because i lost profiles twice so far and with 22 of them it takes ages to revert them. But i would share it for free, why not.
But at the same time i dont want to be made responsible for issues by it.
Sorry, its my first time i would release a C# exe myself, so i may be a bit paranoid.
Any ideas, insight and suggestions are very appreciated
Im aware this can go into legal territory. But for a little freeware app to help others i cant pay a lawyer for this. If there is no way to make sure i cant be made responsible for anything, i simply wont release it.
Is EULA and Terms of Service enough?
Or do i have to publish on github with license or something?
I would think terms of service and EULA would be enough. A suggestion would be to have a routine that would save all the old profiles appending a ‘.OLD’ before the program is even functional. This makes backup copies that can be restored. And put that in the documentation. People are like turkeys. They will find exotic ways to harm themselves.
And somewhere in these folders are the controller profiles. Not all of them are. But every profile has one of these folders.
And again inside one of these folders we have this
So what i wonder about (and im not so sure i want to test this hehe), for the gamepass version one probably would need to replace the whole folder. And then i expect it has to match the index file. That seems binary and i cant changed/update it.
Thats the reson so far it only works with existing profiles.
Basically one needs to create the profile in the sim first, in the case one has lost it (to have the sim register it for the cloudsave) and then use this to be overwritten for the backup.
What the backup does is it switches only the content inside the device tag in a profile xml. So the shell, with GUID and the container files etc is left untouched.
I have no idea if this is needed but seeing that index file with weird container files make me thing this is the better way. This seems to work perfectly. If i have created the file in MSFS and just switch the content with backup, all is nice and next simstart the backupprofile is there.
I think on steam it may work by simply copy a whole profile.
But i will still think about your idea and probably implement it regardless.
Thanks again!
If someone knows how this works exactly, let me know^^
You could have a pop-up that appears when the program is first started stating that the program, while it has been tested, can damage the sim install if it is mis-used, the user must know what they’re doing, and that it is used at own-risk.
Make the pop-up modal so the rest of the program can’t be used until they click past it. Even make it an agree/disagree, so if they disagree, it quits.
Yes, thats how i have it now. One has to click the user agreement where this warning is mentioned.
I guess im just a bit paranoid because first time i release a windows app and then its one where ppl can mess up things too, at same time.
And what rhumbaflappy said i added too. Even if one has to do it on existing profiles, theres still the possibility ppl chose the wrong one, so i backup the file before overwriting it.
It cant be used in itself by reverting the whole file/rename it back from .OLD but one can use the app for reverting to it of course. Better than nothing.
