MC always prompts me to save the world on exit

Posted by Icewolf on Fri 14 May 2010 05:59 PM — 3 posts, 13,973 views.

Icewolf Fri 14 May 2010 05:59 PM #0

Hi, mushclient always prompts me to save the world file when exiting, even though all my MC objects are temporary.

I tried to diff the versions of my MCL files before and after saving, and found the only difference is in the "data_saved" attributes. I'm using MC 4.43. Is this a known bug and has been fixed in the later versions?

Here's the diff file:


--- a/PKUXKX.MCL        Fri May 14 13:54:08 2010 -0400
+++ b/PKUXKX.MCL        Fri May 14 13:57:43 2010 -0400
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
 <!DOCTYPE muclient>
-<!-- Saved on Friday, May 14, 2010, 1:53 PM -->
+<!-- Saved on Friday, May 14, 2010, 1:54 PM -->
 <!-- MuClient version 4.43 -->
 <!-- Written by Nick Gammon -->
 <!-- Home Page: http://www.mushclient.com/ -->
@@ -8,7 +8,7 @@
 <world
    muclient_version="4.43"
    world_file_version="15"
-   date_saved="2010-05-14 13:53:06"
+   date_saved="2010-05-14 13:54:20"

    auto_say_override_prefix="-"
    auto_say_string="say "
@@ -107,7 +107,7 @@
 <triggers
    muclient_version="4.43"
    world_file_version="15"
-   date_saved="2010-05-14 13:53:06"
+   date_saved="2010-05-14 13:54:20"
   >
 </triggers>

@@ -116,7 +116,7 @@
 <aliases
    muclient_version="4.43"
    world_file_version="15"
-   date_saved="2010-05-14 13:53:06"
+   date_saved="2010-05-14 13:54:20"
   >
 </aliases>

Nick Gammon Australia Forum Administrator Sat 15 May 2010 10:29 PM #1

It must think you have changed something. Some things that might be doing this are (apart from the obvious ones):

SetOption or similar to change world configuration
Importing XML from a file or clipboard
Loading a plugin (or deleting one)
Adding a trigger/timer/alias even if marked as temporary (this might be a bug) - if done through the GUI dialogs

Nick Gammon Australia Forum Administrator Sat 15 May 2010 10:53 PM #2

There was a bug in 4.51 where if you added a trigger, alias or timer marked "temporary" through the GUI interface, even though it wouldn't be saved to the world file, the file was still marked for saving unnecessarily.

This has been fixed in version 4.52.