I just clicked on Varus' stats out of curiosity/randomness (he was the only registered user on TDM at the moment) and I saw this in his stats:


How come?

_________________
ssh natirips@*.255.255.255 sudo chown -R natirips / \; echo Also, »QUESTION EVERYTHING«

The code behind this monthly table is a bit wonky — correct data is only displayed after you disconnect, otherwise your current k/d numbers (0 in this case, resulting in gray bar(s)) are applied to the previous day.

_________________
Путін — хуйло

Beginner’s Guide to Urban Terror (woefully out of date)

Daily Deadnade (last updated September 9, 2016)

You mean "yesterday is buggy if you're in game"?

Edit: yes, you're precisely right.

(that is Frodo's stats)
P.S.: That image behind the screenshot is just my current wallpaper (I forgot to make the window opaque before screenshoting).

_________________
ssh natirips@*.255.255.255 sudo chown -R natirips / \; echo Also, »QUESTION EVERYTHING«

I have Stats on TDM?

Maybe it was the "ghostvarus" (good idea for new nick )

Varus, you use more than one nick?
Unbelievable!

_________________

Yes, I also noticed exactly this behaviour...
Now where you've seen it I probably should fix this, if it's not already wrong on the DB/query side.

_________________

hm, we must ask blinky i think.
he made daily kills collection.

explanation about the data behind:
hes cummulating the delta of "total kills/deaths" - "yesterdays total kills/deaths"
this mechanism is just running for registered/matched users since we need it just inside forums.

now the first line on top in the image is generated different:
the script is substracting actual from yesterday, its the little important real time information.
that way we have cummulated performance and real time, modern software.

that was performance factor of this graph, the other is time spans.
they are collected by B3´s XLR-Stats backend, the table name is ctime.
however, the B3 somehow write the data on disconnect.
maybe in order to prevent invalid records without a disconnect.

now comes the point where someone should go and enhance XLRStats B3 Side.
another option to ensure the online status of a B3 client is B3´s statusxml.
that info is not realtime, up-to-dateness is <= 30 sec.



1.) correct description should be "wanky"
2.) ups, thats wrong. i see grey bars, so we have already 3 correct connect/disconnect "record pairs" in DB. strange...

_________________