/astat

[Smurfling]

Hmm in the game chat there's the client sending /astat <username> instead of /stats <username>.

As far as i have seen there isn't a difference in the result, both will display the stats. Or have i missed there something and there's a difference?

[tA-Kane]

I beleive the biggest difference is /astat (short for auto stats) is sent automatically, whereas /stats is not.

[iago]

My guess is that it is asynchronous.  If you send, say, /whoami and /stats right after each other, and /stats is processed first, it will still wait for /whoami to finish before displaying /stats, whereis /astat waits for nuttin' and no one.

I've never tested this, though!

[Banana fanna fo fanna]

Maybe it doesn't affect antiflood?

[Yoni]

Maybe it doesn't affect antiflood?

Try making a game and having 7 people join quickly. You will get IPbanned for flooding with 7 /astat's. That is something that SCE fixes (it disables the automatic /astat).

[iago]

Maybe it doesn't affect antiflood?

Try making a game and having 7 people join quickly. You will get IPbanned for flooding with 7 /astat's. That is something that SCE fixes (it disables the automatic /astat).

Yes, I fixed that too.. battle.net *should* make sure that /astat doesn't flood, and maybe at one time it did, but it doesn't now.

[Skywing]

My guess is that it is asynchronous.  If you send, say, /whoami and /stats right after each other, and /stats is processed first, it will still wait for /whoami to finish before displaying /stats, whereis /astat waits for nuttin' and no one.

I've never tested this, though!

All stats and profile queries are asynchronous.

[iago]

My guess is that it is asynchronous.  If you send, say, /whoami and /stats right after each other, and /stats is processed first, it will still wait for /whoami to finish before displaying /stats, whereis /astat waits for nuttin' and no one.

I've never tested this, though!

All stats and profile queries are asynchronous.

Then what's /astat do?

[Skywing]

Then what's /astat do?

The same thing as /stats, apparently.  A theory I had was that (a)utomatic stats queries would be given a lower priority than manual ones, but there's no easy way to prove or disprove that.

[Arta]

That's what I thought too, but there's no difference that I can see - sending about 3 or 4 /stats commands in quick succession produces a "Too many server requests" message just like /astat does.

[tA-Kane]

Maybe there used to be a difference... but now there isn't and, Blizzard being lazy, they never took it out because they didn't want to make a new patch just so the user wouldn't get "Unrecognized command" message everytime someone joined a game?

[Arta]

That would be my guess.

[Skywing]

That's what I thought too, but there's no difference that I can see - sending about 3 or 4 /stats commands in quick succession produces a "Too many server requests" message just like /astat does.

The "Too many server requests" is unrelated - it's simply a limit on the number of database queries a user can make in a given amount of time.

I don't think that you (one user) will have much of a hope of accurately measuring any prioritization when there are, say, 200000 other users online, many of which bound to be making their own queries indirectly or directly.

[Arta]

That limit isn't calculated per-user?

[FyRe]

I can't seem to find a difference either.  The response time for both seem the same and they both go into a queue at overflow.
My guess is that it's similar to the /w, /m, /msg, /whisper