Page 2 of 2

Re: stats logging.

Posted: 12 Oct 2011, 21:58
by zwzsg
Sounds too complicated. Just award the entire kill to the lucky last bullet, and use the time saved to implement APM. It doesn't matter that you believe Spring is superior enough to make APM irrelevant, plenty of people are so used to measure their RTS performance by means of APM that your product will be felt incomplete if it doesn't feature it.

Re: stats logging.

Posted: 12 Oct 2011, 22:16
by smoth
In gundam I wouldn't log it z :p it was a consideration for ba peeps, so it is low priority IMO. ESP with no way in my understanding to tell what is a command.. I don't know what the expectation of the stat is.

Re: stats logging.

Posted: 12 Oct 2011, 22:23
by zwzsg
Bah just count mouse clicks and keypresses!

Doesn't matter if the measurement method isn't 100% scientifically sound, I just want a number that gets bigger the more I clickety-click.

Re: stats logging.

Posted: 12 Oct 2011, 22:40
by smoth
That means spectators would have high apm.


Is apm commands issued to units? If so does custom formations drive that up?

Is it hotleys pressed etc.

I do not believe chatting should count and no I am not going to write code that checks if you are typing/just clicking an empty pixel.


What is really apm?

Re: stats logging.

Posted: 12 Oct 2011, 23:21
by zwzsg
smoth wrote:What is really apm?
Increment counter on those two callins:
(Make sure the priority is set so they catch actions before every other widget/gadget, and to not return true so they don't eat the action.)
  • MousePress()
  • KeyPress()
- Does not catch orders sent by widgets
- Does not catch text typed for chatting
- Does catch keys and clicks that do nothing

Stop looking for excuse and just use that. Nothing is perfect, but that's no reason to refuse what's only 99% good.

Re: stats logging.

Posted: 12 Oct 2011, 23:44
by smoth
Sounds fine by me. Why do you say before?

Re: stats logging.

Posted: 13 Oct 2011, 00:16
by zwzsg
Whenever a widget/catch return true on these callin, it means it "takes" it, and it's not available for other widget/gadget.

Re: stats logging.

Posted: 13 Oct 2011, 00:21
by smoth
Ok will do.

Re: stats logging.

Posted: 17 Oct 2011, 19:07
by Jools
zwzsg wrote:[
Stop looking for excuse and just use that. Nothing is perfect, but that's no reason to refuse what's only 99% good.
Maybe not when it's 99% good, but when it's, say 30% good, then the question comes why use it at all, you just present a lot of information that has no value. Then it's better to use that screen area (and energy to make the function) to something else.

Re: stats logging.

Posted: 17 Nov 2011, 13:22
by Jools
Is it possible to add a tab to the native endgame statistics window, and in there include the thing that smoth proposes?

Or do you have to completely replace the existing stats window?

Re: stats logging.

Posted: 20 Nov 2011, 11:25
by knorke
Is it possible to add a tab to the native endgame statistics window
not possible. That endgraph is pretty messed up anyway, eg the scaling and other things.

Not really stats logging but related:
When spectating games I sometimes like to compare unit counts, eg who has most fighters on patrol or most nanos
etc. But it is annoying having to select units manually, ctrl+z and all that, so made this:
Image

It shows how many units of each type a player has. The percent number shows the average health of those units.
For most mods several similiar units would probally have to be grouped together to keep it readable, eg for *a AK&Peewee would count towards the same number, or even just have "T1 Kbot."
Probally cba to add that but maybe for inspiration.

Re: stats logging.

Posted: 20 Nov 2011, 12:56
by Jools
Cool.

I wanted to include a part of my stats widget in xta as end game statistic, it would look like this (from the wakka game, red is knorke, grey is dnw and yellow are ray and me):

Image

But then we would have to redesign the whole thing, becausew clicking and closing many windows after the game is not fun.