This forum is a read-only archive of the Gammon Software forum (2000–2026). No new posts can be made. Search the archive.

Auto-logging to file on connect

Posted by Captainbarlow on Thu 09 Mar 2017 03:46 AM — 9 posts, 32,975 views.

Captainbarlow USA #0
So, rather similar to
Template:post=13421
Please see the forum thread: http://gammon.com.au/forum/?id=13421.
I'm having a bit of an issue getting auto-logging to work properly. As implied by mentioning the previous forum post, I read through it and attempted to use the advice there to solve my problem, but I'm simply not seeing it working at all.

Relevant specifics:

Windows 10 / MushClient v4.94

World settings relevant window: https://www.dropbox.com/s/vi2kpqvyc9bqb0h/logging%20window.PNG?dl=0

(This is identical for all 3 worlds I'm trying to auto-log from. Except that they all have very slight, <10 characters, differences in the preamble and log-to windows. The 3 "worlds" aren't, they're simple categories of output from a single MUSH, so the preamble and log-to each reflect the individual "world" they're logging.)

So the problem:

It doesn't seem to actually do anything. No files, text/html/anything show up in my logfile!

I'm not sure what's going on here. The possibility exists that this is a PEBCAK issue (I'm not a coder or a programmer by any means) but the window options seem simple and straightforward enough that I doubt that.

I've tried restarting MC, and checking both after restart and with MC completely not running. No change.

Please, I'd appreciate any help you can offer with this.
Nick Gammon Australia Forum Administrator #1
I suggest you try a different directory. Windows 10 will tend to redirect away stuff you put into "Program Files" into some other place.

In fact you might want to install MUSHclient entirely elsewhere, such as "Documents".
Captainbarlow USA #2
I suspect that that worked. I now have text files present even while connected and (hopefully) logging. Thanks, Nick.

I'll reply to this thread again if I find it's still not working correctly, but I should know that by tomorrow.
Captainbarlow USA #3
.. or not. I broke something in the transition to Documents (or in the transition to 5.05 which I took the opportunity to install.)

One of my plugins is now looking for a file in Program Files still, even though the entire MC installation is in Documents. 

[WARNING] C:\Users\capta\Documents\MUSHclient\worlds\plugins\Background_Image.xml
Line   68: C:\Program Files (x86)\MUSHclient\worlds\plugins\constants.lua contains an invalid path. (Not loaded)
Nick Gammon Australia Forum Administrator #4
You can probably open the file Background_Image.xml and delete line 68 which attempts to load in constants.lua.

Alternatively, put the correct path there.
Fiendish USA Global Moderator #5
It seems pretty unlikely that the file is being referenced by a non-relative path, though. Is it possible that an old registry key is still affecting a load path?
Nick Gammon Australia Forum Administrator #6
Possibly, if the OP simply copied his installation folder, rather than re-installing.
Captainbarlow USA #7
Turns out the file had a simple name there, and didn't bother with a directory path at all? Don't know why it didn't work, but I added in the directory and it's no longer warning me.

Now I just need it to work. :P But I won't bother you guys for a background image not showing up. And thanks again.
Nick Gammon Australia Forum Administrator #8
Possibly another relative path (the image that is).