Clickable Maps Option

[FabledIntegral]

Concise description:
Have an option to "allow" clickable maps if it can somehow be regulated. Just as you can have fog of war on/off, this allows clickable maps to either work or not. Somehow possibly the coding of the site blocks the greasemonkey script from working.

This will improve the following aspects of the site:
Lot of people complain about CM - personally I like them. However it would allow people who want to play speed freestyles without them not to have to make a private game for them or something. And it would ensure in those games that people don't lie and use them anyways.

[ParadiceCity9]

Ya this is a good idea. This really would shut up all the oggiss's out there...

[yeti_c]

The script is an "after the event" add-on... to make it disableable from the site - would be very easily overridable for anyone with even a minor skill in programming.

C.

[FabledIntegral]

I do not have any skills whatsoever in programming.

[yeti_c]

I do not have any skills whatsoever in programming.

And I suspect that even you would be able to disable the override... given the correct knowledge - which would be leaked within days of this happening.

C.

[chipv]

The script is an "after the event" add-on... to make it disableable from the site - would be very easily overridable for anyone with even a minor skill in programming.

C.

Disagree on this one.

You could make it extremely difficult to get around by changing/removing CM site dependencies (you know what I'm talking about) for the disabled case.

A rewrite of CM to cope with both cases of enabled and disabled, not necessarily trivial for the average person.

So long as the programming guys shut up about it and don't try and workaround it (so leave CM screwed for the disabled case), most people would not be able to bypass this.

[cicero]

Better yet incorporate clickable maps into the site.
Which is what I hoped this thread was suggesting.

[yeti_c]

I disagree - all it would be would be some renaming of variables gleaned from the main pages - (Not that Lack would like to do that either as he'd have to rewrite half of his JS files to do it too)...

Especially as he'd planned on adding this to the site anyway.

C.

[FabledIntegral]

Tbh - my suggestion for CM was to get rid of the "auto advance" button as well as the auto attack. Keep it so you can begin turn, fortify, refresh, deploy, attack normally, advance when clicking the territory. Slows things down to like a country every other second (probably conquer 3 territories in 4-5 seconds vs conquering 3 territories in 2 seconds).

[yeti_c]

Yeah once added to the site - none of the "advanced" features would be there...

I suspect only the ability to select territories by clicking on them would be present...

Auto Advance & Preset Auto Attack wouldn't be.

C.

[yeti_c]

Also - if you did have a "disabled" version of CM - then you might create a black market for someone to code round it...

Thus giving some players an advantage over others - which is less fair than the current situation.

C.

[chipv]

I disagree - all it would be would be some renaming of variables gleaned from the main pages - (Not that Lack would like to do that either as he'd have to rewrite half of his JS files to do it too)...

Especially as he'd planned on adding this to the site anyway.

C.

That's not the only way to cripple CM.

[chipv]

Also - if you did have a "disabled" version of CM - then you might create a black market for someone to code round it...

Thus giving some players an advantage over others - which is less fair than the current situation.

C.

I agree with this hypothetical situation, sure.

[yeti_c]

I disagree - all it would be would be some renaming of variables gleaned from the main pages - (Not that Lack would like to do that either as he'd have to rewrite half of his JS files to do it too)...

Especially as he'd planned on adding this to the site anyway.

C.

That's not the only way to cripple CM.

Of course - but anything that you could come up with - could be coded around.

C.

[chipv]

I disagree - all it would be would be some renaming of variables gleaned from the main pages - (Not that Lack would like to do that either as he'd have to rewrite half of his JS files to do it too)...

Especially as he'd planned on adding this to the site anyway.

C.

That's not the only way to cripple CM.

Of course - but anything that you could come up with - could be coded around.

C.

No it couldn't. Javascript does not have the same access that PHP does.
If the PHP does not provide enough information in the delivered web page, there is nothing the JS can do about it.

Your point about a black market stands.
Your points about people with minor programming skills being able to bypass this does not. That is the only point I was making, nothing more.

[yeti_c]

No it couldn't. Javascript does not have the same access that PHP does.
If the PHP does not provide enough information in the delivered web page, there is nothing the JS can do about it.

Yeah but - the site doesn't run on PHP alone - there is a fair bit of Javascript there - that would probably leave the access open for CM to use... rewriting the pages so that JS isn't would be a lot of work...

Also - GM has further reaching powers than standard JS.

As Cicero says - I'd rather Lack spent the time implementing CM into the site proper... instead of wasting time trying to guard against it.

C.

[yeti_c]

Looks like the main thing to do - would be to remove the div "armies"...

But then the script would be able to get this by doing an AJAX request to the server...

Any and all of the info required is also available from an AJAX request at the moment...

Whether or not it needs to be - is the point.

But if you disable CM - then you would also disable BOB... as the information is wanted by both.

But CM could work around that... all it needs - is the XML (for co-ords) and it can get the list of your territories from the drop downs...

It wouldn't have as much info as before - but could still a workable script.

C.

[chipv]

No it couldn't. Javascript does not have the same access that PHP does.
If the PHP does not provide enough information in the delivered web page, there is nothing the JS can do about it.

Yeah but - the site doesn't run on PHP alone - there is a fair bit of Javascript there - that would probably leave the access open for CM to use... rewriting the pages so that JS isn't would be a lot of work...

Also - GM has further reaching powers than standard JS.

As Cicero says - I'd rather Lack spent the time implementing CM into the site proper... instead of wasting time trying to guard against it.

C.

The javascript does not have to be in an accessible .js file.
Imagine some of that code pulled out and instead output via <script> tags in the PHP conditionally.

JS and GM can't reach what isn't there.

Even if lack coded this into the site, there is nothing stopping you running a CM script on top of the disabled part of it so
you would still need to guard against it.

[yeti_c]

I'll restate incase you missed it...

CM could work around that... all it needs - is the XML (for co-ords) and it can get the list of your territories from the drop downs...

It wouldn't have as much info as before - but could still a workable script.

C.

C.

[chipv]

I'll restate incase you missed it...

CM could work around that... all it needs - is the XML (for co-ords) and it can get the list of your territories from the drop downs...

It wouldn't have as much info as before - but could still a workable script.

C.

C.

CM uses unsafe window. I'm hoping I don't need to say more about that without giving it all away.

You're still missing the point - it is not trivial for a person with minor programming skills to get around this.
That is all I actually wanted to point out without giving away methods to both disable it and get around it.

[yeti_c]

I'll restate incase you missed it...

CM could work around that... all it needs - is the XML (for co-ords) and it can get the list of your territories from the drop downs...

It wouldn't have as much info as before - but could still a workable script.

C.

C.

CM uses unsafe window. I'm hoping I don't need to say more about that without giving it all away.

You're still missing the point - it is not trivial for a person with minor programming skills to get around this.
That is all I actually wanted to point out without giving away methods to both disable it and get around it.

Yes I agree disabling CM - in the realm of removing the JS via PHP - would definitely make it a lot harder to recode...

In the above example of how to code round it - you wouldn't need unsafeWindow though?

(As already also stated - removing all the JS would disable BOB too - although perhaps that is also what is wanted?)

So - to disable it in a way that is to allow BOB to remain - would be very simple to code around...

However - to disable both scripts - then only CM could code around.

C.

[chipv]

I'll restate incase you missed it...

CM could work around that... all it needs - is the XML (for co-ords) and it can get the list of your territories from the drop downs...

It wouldn't have as much info as before - but could still a workable script.

C.

C.

CM uses unsafe window. I'm hoping I don't need to say more about that without giving it all away.

You're still missing the point - it is not trivial for a person with minor programming skills to get around this.
That is all I actually wanted to point out without giving away methods to both disable it and get around it.

Yes I agree disabling CM - in the realm of removing the JS via PHP - would definitely make it a lot harder to recode...

In the above example of how to code round it - you wouldn't need unsafeWindow though?

(As already also stated - removing all the JS would disable BOB too - although perhaps that is also what is wanted?)

So - to disable it in a way that is to allow BOB to remain - would be very simple to code around...

However - to disable both scripts - then only CM could code around.

C.

Not all of the JS needs to be removed ... (enough details??)
Combine all methods to disable CM and then look at the combined effort to get it working - trivial or non-trivial?
I have a feeling you will say trivial, and then I will disagree again, the circle continues but ultimately doesn't matter.
What's trivial to you may not be trivial to the average programmer, take it as a compliment.

What I think we do agree on is the amount of effort required to try and make CM disabled whether integrated on site or not.

That's it , really, didn't want to bleed information all over the thread.

[yeti_c]

Not all of the JS needs to be removed ... (enough details??)

Any of the JS needed to be removed would also invalidate BOB.

Combine all methods to disable CM and then look at the combined effort to get it working - trivial or non-trivial?
I have a feeling you will say trivial, and then I will disagree again, the circle continues but ultimately doesn't matter.
What's trivial to you may not be trivial to the average programmer, take it as a compliment.

What I think we do agree on is the amount of effort required to try and make CM disabled whether integrated on site or not.

That's it , really, didn't want to bleed information all over the thread.

As I stated in my last post - it depends on what methods are used - and what the end goal is...

C.

[chipv]

Not all of the JS needs to be removed ... (enough details??)

Any of the JS needed to be removed would also invalidate BOB.

Does BOB use submitButton, quantity, updating? I don't see it my version. CM uses them.

[yeti_c]

Not all of the JS needs to be removed ... (enough details??)

Any of the JS needed to be removed would also invalidate BOB.

Does BOB use submitButton, quantity, updating? I don't see it my version. CM uses them.

BOB uses Armies... which is the main thing that CM uses.

C.