ATTENTION COOLMON USERS, important read!

[muddocktor]

Please discontinue the use of the Coolmon scripts until further notice as it is the Coolmon scripts that are fubarring the EOC stats by hammering Jason's server.

Thanks in advance for being understanding of the problem this is causing.:)

I'm sure that T1 or someone will rewrite the scripts so that they won't do this in the future and then we should be able to use Coolmon again.

[pseudonym]

Ahhhh, so thats what it was. Glad I didn't use it. I call NOT ME :)

[csimon]

I don't believe that it's the script itself causing the trouble but the frequency of the scheduler manager. I think that setting the "scheduled tasks" function to a frequency of not less than every 3 hours would be sufficient but as mudd said please discontinue until further notice.

[muddocktor]

I don't believe that it's the script itself causing the trouble but the frequency of the scheduler manager. I think that setting the "scheduled tasks" function to a frequency of not less than every 3 hours would be sufficient but as mudd said please discontinue until further notice.

With that said, it would probably be better if Coolmon got it's stats directly off the Stanford servers instead of pulling them off of the EOC server.:) Their servers should be the default for stats anyways as they are what everyone else's stats pages pull their figures from.

[mmonnin]

In fact there will be a new Version2 of the EOC stats out soon so dont even worry about recoding it. Soon you will be able to pull of certain stats for yourself so you wont have put request all 15 pages that have calculations on them for Coolmon.

[t1rhino]

The script gathers information that stanford does not provide. It is a combination of the script and the frequency that was causing problems.

[csimon]

the frequency is the issue however ...

[EOC_Jason]

Guys, you can continue using it, however to reduce the number of calls it makes (instead of the 15 simultaneous requests), you can modify the query string in the script to add a "perpage=x" where x is some arbitrary number that you want to be displayed on a single page. So if you know your ranking is in the top 5 you could display just 10 to be safe and it will only return the top 10 people on the team.

I've modified the original vbs script with the perpage variable and taken out the looping, so now it only makes one request.

Oh yeah, and only have it query once every 3 hours or so... ;)

Enjoy.

[t1rhino]

Nice modifications Jason. If you get the xml output for stats working, we can modify it again to reduce the server load even more.

[EOC_Jason]

Yes, definitly. :)

[csimon]

...you can modify the query string in the script to add a "perpage=x" where x is some arbitrary number that you want to be displayed on a single page. So if you know your ranking is in the top 5 you could display just 10 to be safe and it will only return the top 10 people on the team.

Oh yeah, and only have it query once every 3 hours or so... ;)

Enjoy.

so can I change mine to "perpage=1"? :fold:;D:fold:

[t1rhino]

so can I change mine to "perpage=1"? :fold:;D:fold:
:skeptic:

Watch your back csimon!!! :canflag:

[csimon]

:skeptic:

Watch your back csimon!!! :canflag:
ya I noticed ...ok I'll set "perpage=2" justin case! :respect:

[fatcat]

so can I change mine to "perpage=1"? :fold:;D:fold:

:Pwned:

:D

[csimon]

:Pwned:

:D
TeamID = "93"
Username = "csimon"
UserID = "3128"
PerPage = ":rockon:"

[primesuspect]

rub it in, tough guy... Rub it in.... :werr:

[csimon]

aren't you like a day or so away from going red? :celebrate

[TheSmJ]

THanks Jason.

I'll switch to the new script as soon as I get the chance!

[muddocktor]

Since this problem seems to be sorted out, it's time to unsticky this and let this thread die a noble death.;)