watch game

by **codierose** on Fri May 24, 2013 6:47 pm

Operating System: 7
Browser: foxy
Scripts/third party programs used: watched games

Concise description:

Specifics:

watched games no longer working i have 21 watched clan games but when i try to open link nothing happens

by **ender516** on Fri May 24, 2013 6:58 pm

I am moving this to its proper spot in Tools Suggestions & Bugs. At some point I may merge it with similar topics. There does seem to be a lot of reports about this, but I want to be sure we are all talking about the same script.

by **codierose** on Fri May 24, 2013 7:02 pm

is this got anything to do with the update today :?:

by **ender516** on Fri May 24, 2013 7:10 pm

Almost certainly. I am not familiar with the workings of this script, nor the details of the update, but changes to the site can pull the rug out from under a script.

by **codierose** on Fri May 24, 2013 7:27 pm

that sucks
thanks for the quick reply

by **ender516** on Fri May 24, 2013 8:33 pm

The word from the admins is that the Conquer Club API used by many scripts has been disabled temporarily as it apparently was implicated in the problems that the site experienced this morning.

by **thunderhue** on Sat May 25, 2013 7:50 am

Thanks for the confirmation and update.

by **greenoaks** on Sat May 25, 2013 5:26 pm

ender516 wrote:The word from the admins is that the Conquer Club API used by many scripts has been disabled temporarily as it apparently was implicated in the problems that the site experienced this morning.

how does the API suddenly develop problems? was there a hack? is the problem similar to the one we had a while ago where Integers are capped at a ridiculously high number, which of course our game numbers reached?

some insight into the situation would be great but keep the explanation simple

most of us don't have degrees in computing.

by **ender516** on Sat May 25, 2013 6:18 pm

greenoaks wrote:
ender516 wrote:The word from the admins is that the Conquer Club API used by many scripts has been disabled temporarily as it apparently was implicated in the problems that the site experienced this morning.

how does the API suddenly develop problems? was there a hack? is the problem similar to the one we had a while ago where Integers are capped at a ridiculously high number, which of course our game numbers reached?

some insight into the situation would be great but keep the explanation simple most of us don't have degrees in computing.

I have little in the way of details, but it seems that API accesses were consuming excessive processor time. Perhaps a change in the underlying database as part of an update left the API code in a bad way.
In any case, the API seems to be enabled again, so the scripts should be working now.