Reliable way to block Opera 12 and down

[ThreePinkApples]

I'm looking for a fully reliable way to block Opera 12 and down.

The only way to detect it reliably is the javascript 
 

var isOpera = !!window.opera;

which works fine. The problem I have is, is there some way for people to block this specific JavaScript?
I have it running on every page so it will run each refresh so the block have to apply each page load.

Can an extension do that?

Or can an extension maybe just block all redirects so I can't send them away from the page to another?

 

Need ideas.

This is for a game that have troubles with people using Opera to do things that have taken care of in other browser, but we seem to not be able to stop it in Opera 12 and below.

Since it is an old browser anyways we do not see any problem blocking it completely 

[SIGSEGV]

Yes an extension can block that (you don't even need to use an extension, you can just turn off javascript)

[ThreePinkApples]

Yes, but turning of JavaScript will brake the site, so that won't solve anything. I am looking (if it exists) for a method that can block a specific JavaScript if you know what it is (just look at it in other browsers)

[SSL]

Who cares. Detect their browser, post a warning, and leave it at that.

[ThreePinkApples]

Who cares. Detect their browser, post a warning, and leave it at that.

We care, because they are sort of cheating, without cheating. They are giving themselves an unfair advantage that we feel is not good enough to ban them, but we don't want it in the game

[SSL]

We care, because they are sort of cheating, without cheating. They are giving themselves an unfair advantage that we feel is not good enough to ban them, but we don't want it in the game

 

Anything can be spoofed so using browser detection is only so reliable.

[ThreePinkApples]

 

Anything can be spoofed so using browser detection is only so reliable.

But you have no idea how? I googled for a good while, but couldn't find anything. We are looking into other options too so, hoping to find a solution fast as this has been a quite long battle with blocking methods and users finding new ones

[SSL]

But you have no idea how? I googled for a good while, but couldn't find anything. We are looking into other options too so, hoping to find a solution fast as this has been a quite long battle with blocking methods and users finding new ones

 

What is it about the browser that is causing problems? Just detect that behavior and disable the game if detected.

[fizzlesticks]

 

 

 

But you have no idea how? I googled for a good while, but couldn't find anything. We are looking into other options too so, hoping to find a solution fast as this has been a quite long battle with blocking methods and users finding new ones

 

They can just download the page and edit the code so nothing in JS will help. The only other option is to have your webserver redirect/block the older browsers but like SSL said, the headers can be spoofed so that won't stop anyone who really wants to get through.

[ThreePinkApples]

But, the code is running on every page load, quite early in the page load. You can see the site by stopping the loading right before it is finished, but then on the next page you have to do it again.

 

Anyways, we found out that they can do it in other browsers to, we had the wrong idea on how they were doing it. We have an idea for a solution so this should be solved, hopefully

[cynexit]

But, the code is running on every page load, quite early in the page load. You can see the site by stopping the loading right before it is finished, but then on the next page you have to do it again.

 

Anyways, we found out that they can do it in other browsers to, we had the wrong idea on how they were doing it. We have an idea for a solution so this should be solved, hopefully

 

Great that you found a more general solution to your problem!

 

But just a quick side note to all this "use javascript to prevent cheating" stuff:

JS is run locally and can be manipulated by the user in every way possible! You might think that it'll work because the code is executed to fast or maybe because you reload it every X seconds, but this is wrong. There are tools like opera dragonfly and many others that can pause the execution of JS for debugging purposes, after that you can edit the code and just let the JS engine run again. It is also possible to break and run the code "step by step" like you would do it with GDB or other debugging software.

 

In the end, you can always automate that. So keep this in mind: JS is never-ever preventing users from doing unintentional stuff on your site. Always do all the important calculations server-side.

 

(Source: Tried to write a multiplayer tower defense game, made the same mistakes during the first run. )

[ThreePinkApples]

-snip-

Thanks for the input!

I sort of knew this already, therefor my scepticism and this thread. Good to hear from some one with experience with a similar thing