WarcraftRealms.com

This is more of an 'issue' than a real bug...

Whn you have the auto-close who window option selected while doing a Census run and a particular /who request gets 3 or fewer results the results of that /who do not get processed into the results - the game doesn't even try to open the social window on 1,2, or 3 person /who results.

As a result, the data collected can be somewhat incorrect. I noticed it on a run tonight when the level 35 results were to many and it had to break it down by race. There were only 3 level 35 Gnomes. After the run finished, I went in and checked and sure enough - no level 35 Gnomes. (I had done a purge prior to taking it).

Yeah, unfortunately there isn't much that can be done about this. If you do a /who and it returns 3 or fewer results, the results are not returned in the /who data.

I'll have to do some experimenting and see if I can come up with a way to grab that data.

I'll second this.... I ran the census on the Horde side of the new Scarlet Crusade realm earlier today, and for /who 21-25 it found three people that didn't show up in the final results. (Yes, Scarlet Crusade is so new that those three people were the highest level Horde on at the time.)

Incidentally, is the character search working right for the new realms? I can't search directly for Inziliel, my troll rogue on Shadow Council, but if I search for troll rogues on Shadow Council her name's in the list. Clicking on the link that should show the profile gives me a no matches found message.

Ah, I found a problem in my new update process.

If the character does not exist, it makes an entry into the characters table, but it only adds a character history entry if the new data is different than the current data.

Since it just added a new character entry, it isn't different so it's not entering a historical entry.

If there are no historical entries then it won't show up in that search function or if you try to view the history directly.

This will correct itself the 2nd time the character is seen but is an issue for brand new characters.


I'll spend some time to fix this later today.

I think I have a fix in place for this, will keep monitoring.