Conquer Club

So, AJAX has been implemented and I already hate it:
- the clock runs on it self, which distracts me a lot and gives a stupid NaN text infront of it. Also it does NOT turn RED when it goeds below 1 min. (I'm a Mac user)
- the auto reload fucked up my deployment. When I wanted to deploy on Limburg it reloaded and it deployed on Drenthe, what's that for bullshit?
- also when you attack anyone the 'animation' behind it is very annoying.

So what do I basically want to say?
GET RID OF AJAX!

It turned red for me.

Gilligan wrote:It turned red for me.

Added that I'm a Mac user

Gah - your poll is misleading...

Your subject is "Get Rid of AJAX" and the Poll question is "Do you like AJAX".

Either way it's immaterial - AJAX is here to stay...

However what you may want to ask for is a better AJAX implementation...

If you pointed out what your problems are in a more useful and concise manner and in the correct forum then these things might happen!

C.

Did you download the AJAX BOB greasemonkey script?

hecter wrote:Did you download the AJAX BOB greasemonkey script?

Jup I did.

yeah-- it doesnt synchronize well for me. it has a 5-6 second time delay after the action. it does this randomly so its more frustrating as well- gives you a heartattack because you've wondered where you've actually deployed or midedployed. also laggs when advancing and attacking troops.........lagging is one thing but this is not synching#-o

Also, sometimes the refresh will be caught for me - I missed a turn in a speed game because of that.

Just the other day I was telling someone about it becoming compulsory and he said he didn't believe that they'd implement it while it was still a mess...

Please, can we at least get the option to turn it off back until the implementation is fixed up?

BladiN wrote:

hecter wrote:Did you download the AJAX BOB greasemonkey script?

Jup I did.

That's why. Disabled it and the clock will go back to normal.

The1exile wrote:Also, sometimes the refresh will be caught for me - I missed a turn in a speed game because of that.

Just the other day I was telling someone about it becoming compulsory and he said he didn't believe that they'd implement it while it was still a mess...

Please, can we at least get the option to turn it off back until the implementation is fixed up?

The problem here is that the map update is just a load of another image - obviously the dice etc - come in quicker than the map update (as the images are smaller - and probably cached on most users browsers)

Lack may be able to make some code that waits for the map image to finish loading before doing anything else (such as loading the dice)

Of course the other problem is - noone complained about this before - AJAX has been on the site for about a month now!?

C.

yeti_c wrote:

The1exile wrote:Also, sometimes the refresh will be caught for me - I missed a turn in a speed game because of that.

Just the other day I was telling someone about it becoming compulsory and he said he didn't believe that they'd implement it while it was still a mess...

Please, can we at least get the option to turn it off back until the implementation is fixed up?

The problem here is that the map update is just a load of another image - obviously the dice etc - come in quicker than the map update (as the images are smaller - and probably cached on most users browsers)

Lack may be able to make some code that waits for the map image to finish loading before doing anything else (such as loading the dice)

Of course the other problem is - noone complained about this before - AJAX has been on the site for about a month now!?

C.

Ya, but you had the option to disable it.

the only problem i have with ajax is when it refreshers during your turn, i would prefer to see if not refresh while your playing in seq and only the image refreshing when in freestyle. There really in no real need for it during your turn

hecter wrote:

yeti_c wrote:

The1exile wrote:Also, sometimes the refresh will be caught for me - I missed a turn in a speed game because of that.

Just the other day I was telling someone about it becoming compulsory and he said he didn't believe that they'd implement it while it was still a mess...

Please, can we at least get the option to turn it off back until the implementation is fixed up?

The problem here is that the map update is just a load of another image - obviously the dice etc - come in quicker than the map update (as the images are smaller - and probably cached on most users browsers)

Lack may be able to make some code that waits for the map image to finish loading before doing anything else (such as loading the dice)

Of course the other problem is - noone complained about this before - AJAX has been on the site for about a month now!?

C.

Ya, but you had the option to disable it.

So you saw it had problems and thought - I know I'll ignore that and wait until it becomes compulsory...

C.

yeti_c wrote:So you saw it had problems and thought - I know I'll ignore that and wait until it becomes compulsory...

C.

No, I haven't had any problems with AJAX, it's just that this is what some people might have done...

yeti_c wrote:

The1exile wrote:Also, sometimes the refresh will be caught for me - I missed a turn in a speed game because of that.

Just the other day I was telling someone about it becoming compulsory and he said he didn't believe that they'd implement it while it was still a mess...

Please, can we at least get the option to turn it off back until the implementation is fixed up?

The problem here is that the map update is just a load of another image - obviously the dice etc - come in quicker than the map update (as the images are smaller - and probably cached on most users browsers)

Sorry, how does this explain that while waiting for an opponent to finish his turn, it just won't load at all?

The1exile wrote:

yeti_c wrote:

The1exile wrote:Also, sometimes the refresh will be caught for me - I missed a turn in a speed game because of that.

Just the other day I was telling someone about it becoming compulsory and he said he didn't believe that they'd implement it while it was still a mess...

Please, can we at least get the option to turn it off back until the implementation is fixed up?

The problem here is that the map update is just a load of another image - obviously the dice etc - come in quicker than the map update (as the images are smaller - and probably cached on most users browsers)

Sorry, how does this explain that while waiting for an opponent to finish his turn, it just won't load at all?

Can you explain what you mean a bit better? And are you sure what you're describing isn't the "backup slowdown" problem...?

C.

C.

yeti_c wrote:So you saw it had problems and thought - I know I'll ignore that and wait until it becomes compulsory...

C.

No, in my case I saw it had been enabled and it was messing with my monkey, plus I didn't like it sine it would keep throwing me off in RT games, so I figured I would rely upon the thousands of other CC users who don't have my playing options and preferences to report problems.

yeti_c wrote:Can you explain what you mean a bit better? And are you sure what you're describing isn't the "backup slowdown" problem...?

C.

I was playing 1vs1 on the italy map versus nesterdude and I though he'd forgotten to end his turn, since I was clicking refresh, and it got stuck in "loading..." instead of refreshing to show that he'd finished his turn and it was mine.

When it reached 0 seconds and nothing happened, I realised something was up and had to quit firefox, open CC again, tried opening the game, didn't work, so went into another game (which would open) and pasted the game# into the address bar, by which time I had 11 seconds left and missed my turn.

It seems mostly to be a problem with the refresh map link, since using F5 usually works (relatively) fine.

BladiN wrote:- the auto reload fucked up my deployment. When I wanted to deploy on Limburg it reloaded and it deployed on Drenthe,

I also had the mis-deploy problem... (It was a long weekend and my brain is a tad fuzzy.. so i could be wrong) but i selected, re-checked on the map that i had chosen the optimum territory for the attack, I then clicked and it placed on the wrong territory. (auto-refresh)

Wasn't there talk of selecting territory for deploy and fort with the cursor?
I imagine that would fix that problem. (naturally i do not comprehend the gravity of making that work!)

Grand work on the BOB by the way Yeti et al it seems to work flawlessly now.

turn the clock off

problem solved

I was shocked when I saw the setting of Ajax was automatically put to Enabled. It makes your games lag and the refreshing is really really annoying. I preferred just clicking refresh map myself I was way quicker that way. I'm not that concerned with misdeployment but I am with the lag and that now when you press refresh map it's different and it annoys me.

AJAX simply messes up freestyle speed games :/

Warsteiner wrote:I was shocked when I saw the setting of Ajax was automatically put to Enabled. It makes your games lag and the refreshing is really really annoying. I preferred just clicking refresh map myself I was way quicker that way. I'm not that concerned with misdeployment but I am with the lag and that now when you press refresh map it's different and it annoys me.

AJAX simply messes up freestyle speed games :/

It stresses the server less with Ajax permanently enabled.

the missdeploy is fixable though ... i imagine?

BladiN wrote:

Gilligan wrote:It turned red for me.

Added that I'm a Mac user

I'm a MacBook user and it works perfectly fine for me.

Now I have to keep refreshing by hand because I don't know how many men I've lost or where mine are after a conquest now. I also lost the listing of how many territories and armies each player had.

gimil wrote:the only problem i have with ajax is when it refreshers during your turn, i would prefer to see if not refresh while your playing in seq and only the image refreshing when in freestyle. There really in no real need for it during your turn

jiminski wrote:
It stresses the server less with Ajax permanently enabled.

the missdeploy is fixable though ... i imagine?

it's not just the missdeployment. It simply screws up freestyle