Delay timer
-
Hybuir
- Gear Dependent Squirrel
- Posts: 1471
- Joined: Tue Sep 06, 2005 6:22 am
- Location: Austin, TX
- Contact:
Delay timer
Before I used to have /censusplus timer .01 with zero delays especially during peak periods. Now the forced timer is 5 minutes. Any way of allowing this again?
-
bringoutyourdead
- Forums Admin & general flunky
- Posts: 1432
- Joined: Fri Nov 07, 2008 1:11 pm
- Location: Texas, USA
You can always force a new Census run with /census start... or the start button from the main window.
hmm...Took a little bit to figure out what you were doing.
I am not sure it was what Rollie intended when he implemented the timer code.
I do have some concerns about how Blizzard looks upon our usage of their API resource.
They have implemented throttling code which limits how many /who queries per x amount of time can be processed per realm database.
They have also disabled /who for levels 1-19.
I don't remember any official reason for taking this action.
{edit see this forum thread and the tweet..
http://us.battle.net/wow/en/forum/topic/13661606111}
When I asked in the WoW forums, players claimed it was to block the guild auto-invites due to a guild benefits hack.
That may be true...
But I don't really believe that is so, as that hack was closed and low level /who is still blocked.
I still find it a bit odd that Blizzard would take away a major tool for new players to find others at their level so they could group together to play.
Blizzard closely guards the actual concurrent player counts and activity characteristics as this is considered business proprietary information.
I wouldn't want to have our addon considered unacceptable to Blizzard management, as they could shut us down very quickly (by changing the throttle or just completely disable that api call.)
To be honest I am not sure what advantage we would have for a continuously cycling Census run.
So at this time I will not be making any changes in that section of code.
But on the other hand I can't stop you from make the change.
CensusPlus.lua line 5634
CensusPlusSlider1:SetMinMaxValues(5,30)
hmm...Took a little bit to figure out what you were doing.
I am not sure it was what Rollie intended when he implemented the timer code.
I do have some concerns about how Blizzard looks upon our usage of their API resource.
They have implemented throttling code which limits how many /who queries per x amount of time can be processed per realm database.
They have also disabled /who for levels 1-19.
I don't remember any official reason for taking this action.
{edit see this forum thread and the tweet..
http://us.battle.net/wow/en/forum/topic/13661606111}
When I asked in the WoW forums, players claimed it was to block the guild auto-invites due to a guild benefits hack.
That may be true...
But I don't really believe that is so, as that hack was closed and low level /who is still blocked.
I still find it a bit odd that Blizzard would take away a major tool for new players to find others at their level so they could group together to play.
Blizzard closely guards the actual concurrent player counts and activity characteristics as this is considered business proprietary information.
I wouldn't want to have our addon considered unacceptable to Blizzard management, as they could shut us down very quickly (by changing the throttle or just completely disable that api call.)
To be honest I am not sure what advantage we would have for a continuously cycling Census run.
So at this time I will not be making any changes in that section of code.
But on the other hand I can't stop you from make the change.
CensusPlus.lua line 5634
CensusPlusSlider1:SetMinMaxValues(5,30)