It's not needlessly complicating things. It's done for a reason; if you don't know of it yet - it doesn't mean it's needless and that it's a complication.
You can still backup the profiles with an external backup as well if you're that clever (I do that for my mudlet profiles), but most people do not setup such a thing, and a good majority who have had their profiles - months worth of work - saved by Mudlet because of this mechanism were genuinely pleased by this behavior (and most of them didn't even know about this feature until disaster happened). Most people aren't concerned with data corruption. Neither they are with security for that matter. But it doesn't mean applications should not care about these things for the user then - because they should, and ultimately, those that do are the better ones. -- You received this bug notification because you are a member of Mudlet Makers, which is subscribed to Mudlet. https://bugs.launchpad.net/bugs/1215034 Title: save profile - less than idea behavior Status in Mudlet the MUD client: New Bug description: Recently my windows manager crashed and it seems despite having been running for several weeks, my latest changes to my mudlet scripts were not saved.... While i understand the "save profile" button solves this, it seems rather unintuitive that mudlet does not save the profile when you are making large changes to the triggers and such when you close the script window or when those triggers become active at least. To manage notifications about this bug go to: https://bugs.launchpad.net/mudlet/+bug/1215034/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mudlet-makers Post to : mudlet-makers@lists.launchpad.net Unsubscribe : https://launchpad.net/~mudlet-makers More help : https://help.launchpad.net/ListHelp
