I don't think this'll be too difficult to add... And it would be very helpful for scripters who require very prescise timing.
When you hover your mouse over a line, you get the time and date stamp.
What I would like to see is also a time between one line and the next in millisecond format.
I.E. From line 1, to line 2, how much time passed between the two, 500 milliseconds, 5 seconds, 1500 milliseconds... Ya know what I mean?
Can you clarify, you want it in the hover text? Or, just available to a script somewhere?
Either or...
Both would be great.
But my inital idea was for hover text, like looking at the timestamp for that line.
Line 3594, Friday, July 14, 12:52:17AM, 500ms
Or something like that... The 500 ms would be the time difference between that line and the prior line.
Perhap allow a bit of customization to the tooltip box.
I'd prefer to just have the military time and line #. The date gets clunky and I don't need miliseconds beyond satisfying my own curioisity with regexp match times.
Well, all I can say is that one of the muds that I play require... very, very accurate timing. And knowing the time difference between the newline, and the prior line would really be helpful. It would help me, I don't think it'd be that complicated to add. I am sure it would help other people as well.
Version 3.76 now has another field you can obtain with GetLineInfo, which is a high-resolution timer. This should give you the ability to compare one line with the previous and work out exactly the time difference.
Bear in mind however the latency of the TCP/IP packets, and that some lines may be batched together into the same packet.
Yes, that thought had crossed my mind, which I don't particularly mind. I'm not worried about that, I imagine it'll just say 0ms.
It will probably be slightly more than 0, as it takes time to process a line (triggers etc.) however it will be small.
I am getting results like this (these are time differences):
0.00008890
0.00008766
0.00009302
0.00008751
0.00007840
0.00020469
0.00009711
0.00013277
0.00006412
0.00004703
1.70075432
0.00009941
0.17542972
2.18646055
0.00017771
0.25949439
0.00007043
0.00006358
0.00005930
0.00006136
0.00006010
0.00006057
0.00005647
0.00006019
The big gaps are when I type in a new command, the small ones are lines in one packet I guess. You can see that many lines are only about 60 microseconds apart.
Is that including blank lines?
Or just lines with information?
The datestamp is a mediocre, semi-accurate facimile of what I'd like to see. Infact, I ended up using it to get a rough idea of timings involved, then narrowed it down from there.
With being able to get a truly accurate time down to the millisecond, I could work things out better.
That's more or less what I was thinking of.
When a line comes in for an attack. I want to be able to see the time it takes, down to the millisecond to when it lands, this of course means letting it land intentionally.
The date stamp always gives whole seconds...
12:52:54 AM
12:52:56 AM
It rounds up or down... It doesn't give you fraction of a second. Knowing the exact time I send a command to the mud(which prepares defense) and when the Defense end(outputs a missed block) is difficult to know when it lasts less than 1 second it just shows it as a whole second.
Also... Does the getlineinf option cover every line on the output, not just lines coming in from the mud?
I.E. When you echo the input, will it show that information as well?
Every line is timestamped, including ones generated at the client end. The timestamp happens at the time the newline is processed.