Noxm wrote:yep i purge the data base each time..
just do that lua change :
Oats wrote:Hey guys,
I was able to come up with a way to fix the census addon given the server's buggy who command.
Here is the change I made to the CensusPlus.lua
REPLACE: if (numWhoResults > MAX_WHO_RESULTS) then
WITH: if (numWhoResults == MAX_WHO_RESULTS) then
The way the server works now, numWhoResults will return 49 even if there are 100 results. By forcing it to break down the 49 results, it should get everyone on the server with each pull.
Yeah I stumbled upon the quoted post in an other thread, cause otherwise Census+ 3.5.1 would just return 49 players as a result of some brackets (most notably Lv.60 when there are in fact about 400-600 of that Lv.)
It went from a 2 min search to up to 15 min scanning though ahah.
But in the end, instead of 638 players found on each side, it resulted in 2300 Horde (530 Lv.60) & 2200 Alliance (350 Lv.60) for a total close to 96.5% of what the /who reported. I put that on the account that it took 2 x 15 min to do a scan of both Alliance & Horde, at 3:30 PM GMT+2
So yeah, crazy good population I would say
In the end it's pretty close to 50/50, except Horde has about 25% of Lv.60 when Alliance has ~ 15% of Lv.60
This is a signature until I can bypass that damned 502 ERROR when I put an IMG tag in my sig and try to submit it.