client.log uses UTC instead of local system time

[SomeAussieGaymer]

I've noticed that the client.log file displays timestamps in UTC rather than the local system time.
For example, my most recent log shows the first entry as:

[2025-06-20 09:46:34]

However, I am in Australia (UTC+10), and the local time at that moment should have been:

[2025-06-20 19:46:34]

While this is a minor issue, using local system time (or at least including the local timezone offset) would improve clarity when reading the logs—especially for troubleshooting and correlating events with other logs or real-world times.

[SDGNelson]

One could argue the same in favor of UTC timestamps: useful for correlating events with other logs! (It's helpful when comparing client and server logs which may be in different time zones. For example, when players submit logs to server host and host shares with us for troubleshooting.) Converting to discussion so others can weigh in.

[DanielWillett]

Maybe it would be better to add UTC or Z after it to make it obvious its in UTC, or print it as a DateTimeOffset so it includes the offset. I think UTC does make it better for comparing like you said.

Also DateTime.UtcNow is a bit faster than Now since the computer has to do timezone conversions, and speed can be important for logs.