The problem with doing this is that already we have a problem with the backup directories being way too big. While we do include a tool to deal with this now, it's non-discoverable, not automatic and has no UI representation.
So saving often like this will cause issues. However, I would agree with having Mudlet save your profile every 24h - so long-running sessions won't completely lose everything if you haven't been saving. -- 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 : [email protected] Unsubscribe : https://launchpad.net/~mudlet-makers More help : https://help.launchpad.net/ListHelp
