|ChatTimestamps 1.8 release||2.41 KB||Aug 16, 2015||6.2.0||4,244||Download|
|Chat Timestamps 1.7.2 release||1.82 KB||Nov 9, 2014||6.0.3||1,628||Download|
|ChatTimestamps 1.7 release||1.81 KB||Nov 9, 2014||6.0.3||223||Download|
|ChatTimestamps 1.6 release||1.58 KB||Oct 15, 2008||3.0.2||15,194||Download|
|ChatTimestamps 1.5 release||1.61 KB||Sep 14, 2008||2.4.3||820||Download|
|ChatTimestamps 1.4 release||1.48 KB||Sep 9, 2008||2.4.3||176||Download|
|ChatTimestamps 1.3 release||1.45 KB||Sep 9, 2008||2.4.3||210||Download|
This very tiny mod adds a customizable timestamp (defaults to [HH:MM:SS] format) to every chat window there is.
v1.04+ support for color coding
v1.05+ support time selectors that remove leading 0 from the hour (#H, #I)
v1.07+ works with chat frames both static (main, combat log, custom tabs) and dynamic (detached whispers, battle.net whispers)
v1.08+ support local time offsets (to displace the timestamps forward or backward), server time (@H, $H, @I, $I, @M, @p, @P), and lower case am/pm format (%P)
While added for completion, it has to be noted that world servers and instances servers might live in different timezones. So for example if the server lives in UTC, and the instance server in UTC+2, the user (by using server times) will see a lapse forward when moving from the world to the instance, and backwards when moving from the instance to the world.
To avoid this problem (for those interested only in server times) offsets have been introduced, allowing the user to set a custom number of seconds as offset from the local time. If the user lives in PST, but the server in PST-2, using the command /cts offset -7200 will adjust the local timestamp to match it.
Additionally it should be noted that offsets will not apply to server time.
Although previously taken for granted and not specified, it is actually possible to set up a format containing year/month/day/week or whatnot. See the examples for more inforamtion.
/cts format [timeformat] – shows (or sets if parameter is passed) timestamp format
/cts offset [seconds] – shows (or sets if parameter is passed) timestamp offset, expressed in seconds
/cts serveroffset – shows the (approximated) offset between local time and server time
Custom Time Selectors
#H – same as %H, but removes the leading zero ("01" becomes "1")
#I – same as %I, but removes the leading zero
@H – server time hour (24h format)
@I – server time hour (12h format)
@M – server time minute
@p – server time AM/PM
@P – server time am/pm
$H – same as @H, but removes the leading zero
$I – same as @I, but removes the leading zero
%P – same as @P, but for local time (was not previously available on certain OS)
Color Codes (v1.4+)
|cAARRGGBB<timestamp format here>|r
AA = Alpha, RR = Red, GG = Green, BB = Blue
In standard chat frames alpha is apparently not used, but it's still recommended to set it to FF
Assuming local time is 14:50:21, while server time 16:50:21
|cFFFF2200[%H:%M:%S]|r – [14:50:21] message
|cFF2288FF[#I:%M:%S %p]|r – [2:50:21 PM] message
|cFF00FF00[@I:@M:%S @P]|r – [04:50:21 pm] message
%A %B %d, %Y – %I:%M:%S %p – Sunday August 16, 2:50:21 PM message
Additional information about time formats can be found here. You can also use this tool to ease the set up of a time format string.
Note that not all the formats are valid on both Windows and OS X, some selectors might be reported as invalid. For example %e (day of the month 1..31) doesn't work properly on some OS, while %d (day of the month 01..31) does.