What the heck? Unsure...

ok, so Clent version: 5.06

Just connected to 'my' game (only MU* I really play on) and had something really weird happen... never happened before.
I use the Daily Log plugin, that lovely thing that closes a log at 11:59:59PM local time, and re-opens it at midnight, as a new log... keeping each log for a single 24-hour period.

Logged off yesterday around 8:40ish PM... logged on at 12:45PM....

In the middle of showing the initial rooms description, client throws out "Restarting log file." in the middle of a paragraph...I thought it was a error when I grabbed and edited the desc the day before, then remembered 2 things: 1: I didn't edit room description at midnight, so it wouldn't have caught that.. and 2, which is really important: I was updating a completely different room's desc.

Opening the logfile, instead of seeing my typical initial logfile beginning: ...the Header I created, the game's ASCII art login screen (big Pegasus, rampant), and the room description, etc... it starts at the paragraph it interrupted.

Again, it's nothing really damaging or anything, just thought that it was REALLY WEIRD that the Daily log plugin, which has so far worked perfectly since I started using it...*years* ago, would activate at around quarter to 1PM... the actual timestamp is 12:45:38PM. It cut off/out 81 lines, from the "connected", through the login screen and MOTD, to the majority of the room's description.

Any ideas as to what could have happened, or just agreement of "that is some weirdness"?

aaand, it did it again today.

Logged on at 12:47:42PM, it threw out the main screen graphic, login, etc, this time however, it got as far as finishing the room's description before showing the "Restarting Log File.", putting it in an actual blank space in the initial information from my Auto Connection @Aconnect, so it lopped off the login and room description, starting just with my list of mail onwards...: Mail, my watch list of who's on, rumors, then time and date... but theres still no indication as to *WHY* the daily log is closing the log AT NOON and opening it back up, basically clipping off the initial portion of the log. Computer's clock is giving the correct time. There was 2 times my taskbar partially stopped working and the displayed clock was frozen on a particular time, but that shouldnt affect anything, rebooted the computer cause closing and restarting
File Explorer didnt fix it like it's "supposed" to.

Can you link to the plugin?

if you explain a little further, maybe... at the very least, I can copy and post the contents of the plugin
I got it from here: https://cagefire2000.tripod.com/MCPlugins/MCPlugins.html, the dailylog.xml plugin, but yeah, here you go, to my knowledge nothing in it has changed since I downloaded and installed it nearly 2 decades ago.. Additionally, have my log files set as <character name> - %b %d, %Y.txt, and it's been working fine for the past 18 years... when I was up and connected past midnight, would get it at a second to midnight, then reopen at midnight, and if I stopped before midnight (be it 6pm, 10pm, 11:30PM), even leaving the client running and the world open but unconnected overnight, when I'd log back on it'd work normally, didnt log me in and try to reopen the log file it was currently using, rewriting it (already have it set to add to logfile, otherwise it'd overwrite every time I had to log off and reconnect throughout the day:

<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE muclient>
<!-- Saved on Friday, August 10, 2007, 1:05 AM -->
<!-- MuClient version 4.08 -->

<!-- Plugin "DailyLog" generated by Plugin Wizard -->

<muclient>
<plugin
name="DailyLog"
author="Malix@8bit"
id="36ef58963eb1bbfb9cb38bf8"
language="JScript"
purpose="Restarts the logfile at midnight"
date_written="2007-08-10 01:04:40"
requires="3.51"
version="1.0"
>
<description trim="y">
<![CDATA[
This plugin will close and reopen the world's logfile at midnight, you /must/ have a logging filename with date substitions set in the world preferences. The plugin will do the rest.
]]>
</description>

</plugin>


<!-- Aliases -->

<aliases>
<alias
script="RestartLogging"
match="RestartLogging"
enabled="y"
omit_from_log="y"
omit_from_output="y"
sequence="100"
>
</alias>
</aliases>

<!-- Timers -->

<timers>
<timer enabled="y" send_to="10"
at_time="y" omit_from_output="y" omit_from_log="y" >
<send>RestartLogging</send>

</timer>
</timers>

<!-- Script -->


<script>
<![CDATA[
function RestartLogging() {
if ( world.IsLogOpen() ) {
world.CloseLog();
world.OpenLog("",0);
world.Note("Restarting Log File.");
}
}

]]>
</script>


<!-- Plugin help -->

<aliases>
<alias
script="OnHelp"
match="DailyLog:help"
enabled="y"
>
</alias>
</aliases>

<script>
<![CDATA[
function OnHelp (sName, sLine, wildcards)
{
world.Note (world.GetPluginInfo (world.GetPluginID, 3));
}
]]>
</script>

</muclient>

Honestly I'm stumped. Is it now happening consistently? Could it be caused by an OS update?

Funny thing is, when I logged on today 12:01:23PM, it didn't throw out the "Restarting Log File." like it did on the 18th at 11:02:16 when I logged on, or 9:45:44AM the 17th, or 1:24:25PM on the 16th so, I honestly don't know what's up with it either, why it started and why it's doing it well after midnight... it didnt do it today cause I went and disabled the plugin but still.... about the only other thing I can possibly think of is something changed with the OS itself with the last update that ran and the computer rebooted...but it shouldnt cause this kind of a problem, right?

It's possible it's due to an OS update, I know that since I learned about the possible Bricking issues of Win 11's latest update or 2, I've been Pausing updates, hoping to avoid it. I turned it back on more or less by accident, cause I disabled and re-enabled the URL hyperlink 2, cause clicking on one link a while back, it gave me an error saying that it couldn't load the url, and when I clicked the enable button, it apparently reenabled both of the disabled plugins, not just the one that was highlighted....and I saw that once again, while it was WELL after *noon*, it's spitting out the "System Log Restarting", again clipping off the initial login screen information.

Though it doesn't seem to do it if I start from a "Fresh" instance... IE: if I leave the client opened and running, but just logout of the specific game world... leaving the previous days output in the output bugger, and the commands in the command buffer... doing /THAT/ and logging in sometime the next day, it will "Restart Log File" ... if I close the world window, or have to reboot the computer, thus clearing the output screen and stuff, it doesn't give me the "Restarting Log File" or whatever. As for updates.... lets see now... the last Feature Update I did was installed 12/12/2024, Win 11 Version 24H2... the last few Quality updates were 11/11/2025, .NET 9.0.11 update for x64 Client, .NET 8.0.22 Update for x64 Client... 10/16/2025 Cumulative Update for Win 11 Ver 24H2 for x64-based systems, Cumulative update for .NET framework 3.5 and 4.8.1 for Win 11 ver 24H2 for x64 then 2 security updates for .NET 9.0.10 & 8.0.21 for x64 client on 10/14/2025

Didn't do it again today, but then again thats probably because I was online past midnight, so it had already Restarted the log, so whatever's happened it only seems to do the restart at strange times if it doesn't restart it *AT* midnight the way it normally should.. IE: if I'm online when midnight hits, it'll restart the log as normal, but if I log off for the night before midnight, be it 4pm, 9pm 11:30PM, whatever, then log on again the next day, it'll act like it didn't perform its log restarting duty and restart the log *then and there* when it finally notices, sort of like someone who overslept and is rushing through their wake-up routine, not realizing that ...hey, don't have to do *this* cause it was done already. (3 Stooges: "We ALL put the yeast in!") ...Of course, it doesnt do that if/when you start from a clean run as opposed to picking up from where you left off. (IE: keep the world window in question open instead of logging off, closing it & opening it again .

New Update... Discovered something interesting and perhaps a little telling?

Ok so, I typically leave the client open, along with my main game world, so I have at least a couple days or more of back scroll of output as well as command buffer.

Had noticed this strange happening with the Daily Log plugin I got (see earlier in feed for url, from cagefire2000's page) where it would "Restart log file" whenever I logged in the next day...could be 1am, could be noon or later, the 1st login of the day it'd semi-randomly "reset" the log, erasing everything above the "reset"

New info... just out of curiosity, I opened a completely new instance of the client, opening a "fresh" instance of that game and that character... Example: Gammon's World - Tester (name the world files by way of <Game Name> - Character Name... so Harry Potter World: America - Toby ... holds similar for the aliases, and trigger files, as well as logs... makes organization easier, espec for playing multiple aliases in the same game to have " <Game> - CharName " tabbed at the top/bottom, to keep track of who you're playing as... but I digress..

As I was saying, opened a new instance, fresh character run... scrolled back, didnt see the "restarting log file", got checked out by another player, so got some "so and so +fingered you / so and so checked your info" ...paged them a greeting and said would be back, having client issues ...disconnected, went to my STANDING instance (took maybe 10 seconds or so), logged on after resetting logon timer (dont need to see "2 days x hours, x seconds connected" when it's just been 10 seconds, throws me off worse than normal) ... it *immediately* dropped a "restarting log file"
Initially logged on at like 11:28:xxAM, maybe :29:xx ..was on for about a minute or so... Just checked the log for the day, it wiped the previous interaction and information, and started fresh-fresh, the logon from the minute or 2 before isn't there just the 11:30:37 AM connection, all because it detected previous info in the output window... Previously: "Disconnected on Saturday, Jan 03, 3036 12:56 PM ..blah blah blah..." timestamp: 12:56:44PM!
11:30:37AM!--- connected on Sun Jan 04, 2026 11:30 AM ---
11:30:37AM!Restarting Log File.
[This is where it wipes away the already created logfile from the "clean" instance of connection a minute or 3 before.

Now again, it never used to do this, I'd left the client up, the game I play 'loaded' just unconnected, then establish connection, it'd load just fine.