anyway to stop people from autoclicking?

The_Imaginarium

SansStudios wrote:
The_Imaginarium wrote:
-snip- :: stack :: #969696
The highest cps is not 14.1, I can easily get higher.
-snip- :: stack :: #969696

However many auto clickers can click every 1/1000 of a second.
Thus if we test this :

reset timer
wait ((1) / (1000)) secs
set [i v] to (timer)

Here are the results I get:
0.02
0.036
0.033
0.027
0.029
0.021
0.022
…

The timer is not counting the time accurately, so we cannot rely on it to detect very small increments.

CloudyWhale

when green flag clicked
set [clicks v] to [0]
forever
wait (1) secs
set [clicks v] to [0]
end

when green flag clicked
forever
wait until <mouse down?>
change [clicks v] by (1)
wait until <not <mouse down?>>
end

when green flag clicked
forever
if <(clicks) > [24]> then
broadcast [hacking detected v]
end
end

Last edited by CloudyWhale (May 7, 2021 14:00:48)

jdmdigital

CloudyWhale wrote:

when green flag clicked
set [clicks v] to [0]
forever
wait (1) secs
set [clicks v] to [0]
end

when green flag clicked
forever
wait until <mouse down?>
change [clicks v] by (1)
wait until <not <mouse down?>>
end

when green flag clicked
forever
if <(clicks) > [24]> then
broadcast [hacking detected v]
end
end

If im reading that correctly, the click count will reset every second as long as flag is active. How will that help?

GuitarGuyPlayz

A1Programmer wrote:
anyone have any ideas to stop autoclicking, maybe a delay or something?

I think you can't autoclick on scratch

jdmdigital

Scratch is a website….there are apps that people use to click ads on websites, why not use those on scratch, thetefore its posible on Scratch

GuitarGuyPlayz wrote:
A1Programmer wrote:
anyone have any ideas to stop autoclicking, maybe a delay or something?
I think you can't autoclick on scratch

dhuls

QuantumCodes wrote:
if he is clicking at more than 8 times a second or he is clicking at the same exact spot for like 5-10 mins then he is a autoclicker.

Ever heard of butterfly clicking, jitter clicking, and drag clicking? These are legit methods that allow you to get higher cps. As for the op, a few Minecraft servers base it off of the consistency of time between clicks. You could try this

when green flag clicked
delete (all v) of [Time v]
repeat until <whatever>
if <mouse down?> then
change [clicks v] by (1)
add (timer) to [Time v]
reset timer
wait until <not <mouse down?>> // Other examples include this
end
end

And then a script to see if it's too consistent (I'm too lazy to do that)

dhuls

CloudyWhale wrote:

when green flag clicked
set [clicks v] to [0]
forever
wait (1) secs
set [clicks v] to [0]
end

when green flag clicked
forever
wait until <mouse down?>
change [clicks v] by (1)
wait until <not <mouse down?>>
end

when green flag clicked
forever
if <(clicks) > [24]> then
broadcast [hacking detected v]
end
end

Some people can click faster than 24 cps. A detector base on consistency is better than one based on speed alone.

The_Imaginarium

dhuls wrote:
QuantumCodes wrote:
if he is clicking at more than 8 times a second or he is clicking at the same exact spot for like 5-10 mins then he is a autoclicker.
Ever heard of butterfly clicking, jitter clicking, and drag clicking? These are legit methods that allow you to get higher cps. As for the op, a few Minecraft servers base it off of the consistency of time between clicks. You could try this
when green flag clicked
delete (all v) of [Time v]
repeat until <whatever>
if <mouse down?> then
change [clicks v] by (1)
add (timer) to [Time v]
reset timer
wait until <not <mouse down?>> // Other examples include this
end
end
And then a script to see if it's too consistent (I'm too lazy to do that)

I ran a test in a post above and found the timer is not accurate enough to reliably detect the time between two clicks.

SansStudios

The_Imaginarium wrote:
... :: color 5
Here are the results I get:
0.02
0.036
0.033
0.027
0.029
0.021
0.022
…

The timer is not counting the time accurately, so we cannot rely on it to detect very small increments.

Hmm, I ran a slightly different test and got the following:

define Click 
reset timer // w/o screen refresh
add (timer) to [clicks v]

when green flag clicked
forever
click
wait (0.01) secs
end

and got a range from 0.30 to 0.35 (other than the first click)
After the first 100 clicks, the list only reported 0.33 or 0.34, which is accurate enough. Even an error of 0.1 seconds is impossible for a human clicking for hundreds of clicks.

Last edited by SansStudios (May 8, 2021 22:05:51)

Discuss Scratch