Setting the timestamp format to have a • character in it no longer works properly whether set in the Options dialog or via /timestamp -f. The timestamp is set, viewable both in the Options dialog and via $timestampfmt but the actual timestamp displayed in the channel is the default [HH:nn]. $timestamp also returns the [HH:nn] style timestamp.

Confirmed on Win7 64bit

Thanks for reminding me: I forgot to include that I'm on Win7 x64 also.

I also just discovered that the same time format supplied to $asctime() is returning $null.

Thanks, it turns out that some CRT library time-related functions fail to work if a string contains a unicode character. I have changed my time evaluation routine to get around this in the next version.