mudlet-makers team mailing list archive

[Vadim Peretokin <vperetokin@xxxxxxxxx>]

They would. As I mentioned, "each one [backup, file] needs to be able to
restore the complete state". Windows corrupts files - it's part of the
reason we do backups. If it corrupts a differential backup, none of the
following ones can be used - rendering them fairly useless!

That's why full backups are necessary every time.

There are ways we can improve their size, but with your idea, for someone
who does a lot of heavy editing and happens to close the edit window,
Mudlet will generate a ton of backups.

But losing weeks worth of work isn't good either. So I think saving once a
day, if you aren't in the habit of using Save Profile, would be better than
the current situation.

-- 
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