I wan't my game to say “Turn Off Turbo Mode” if it is turned on.
Like this game - Sky City (v1.2)

I would think that you could measure the frames per second of the project. Scratch runs at 30 frames per second so Turbo Mode must run at more than 30 frames per second. I would start there. I just made a simple example but I have to try it on another computer to make sure I'm getting accurate results.

On the game I gave as an example it says 120-160 fps when Turbo Mode is on. and 20-40 as normal

So why not create something that checks the the fps at the beginning of the program. If fps < 40 then it is off, else, Turn off turbo

But all the fps script I found here does not change if Turbo Mode is on

This is certainly not ideal but it does seem to work

https://scratch.mit.edu/projects/168596939/

Thx so much! I found out that my problem before was the fps needed to be for only one sprite. Try test my game now!
Block Tree Clicker V0.9

Looks good but on my old laptop your turn turbo mode off screen flashes when there is a spike. Maybe change that fps parameter from 50 to 60.

That is why I was going to test on another computer before posting but I never had a chance. I'll look at your script now.

I have changed it to 80 now because I use auto clicker

The script I used was just an example, but you really only need to check if turbo mode is on when you start the project right? No need to have a look constantly checking the fps if you only require it to start the game. I created a generic checker but in your project, you don't need to loop that forever.

SHould be one check at the beginning. Then it is over because shift clicking the green flag starts over the program.

I was Wrong. But you can add a wait until block in your loop so that it only checks when Turbo? = false

No shift clicking does not starts it over
Try get a lot of money and do it you will not lose anything

I'm on a different computer now. I still get that screen to flash as you have some spikes and dips in your fps. Looks good though, nice project. I'll look to see if I have time to check for a more efficient and accurate system.

Here is the wiki about that.

https://wiki.scratch.mit.edu/wiki/Detecting_Turbo_Mode

Also added autoclicker detector

A much better option is to write your project in such a way that turbo makes no difference to how it runs.

For example, if you have only a single main ‘frame’ control loop in one sprite (or the stage), which broadcasts to all other sprites/clones to do their work for that frame, then you can use the timer to ‘cap’ the rate of that loop (thereby capping the frame rate).

(Also, you will find the single-control-loop method gives numerous other advantages, such as ensuring that things are synchronised across sprites in the way you want by using a chain of broadcasts in the main loop to ensure everything gets run in a well-defined order, as well as making it really easy to add a pause button/key to your project because you only need to put it into that one loop.)

No because i'm working on custom counter where instead of giving the pr/sec amount it just goes faster and with turbo mode it will go too fast. The game is not done at all, so the Turbo Mode tester will be needed to get the best gameplay and without cheating.

If they really wan't to cheat I can make it test if they deleted or removed the costume so the whole game will stop.