Open LeszekSwirski opened 9 years ago
Currently FC uses the requested autoclick speed for time estimates, however this does not necessarily match the actual the real autoclick speed due to browser limitations. If I write
function autoclick() { Game.ClickCookie(); FrozenCookies.autoclickCount += 1; if (!FrozenCookies.autoclickStart) FrozenCookies.autoclickStart = Date.now(); FrozenCookies.autoclickEnd = Date.now(); } FrozenCookies.autoclickCount = 0; FrozenCookies.autoclickStart = null; clearInterval(FrozenCookies.autoclickBot); FrozenCookies.autoclickBot = setInterval(autoclick, 1000.0 / FrozenCookies.cookieClickSpeed)
this shows:
> FrozenCookies.cookieClickSpeed 250 > FrozenCookies.autoclickCount / (FrozenCookies.autoclickEnd - FrozenCookies.autoclickStart) * 1000 74.59526774595268
Adding a realcookieClickSpeed function would make the time estimates much more accurate (and perhaps make purchasing calculations more precise).
realcookieClickSpeed
Agrees. Everyone gets their clicking speed to full, while their browser just can't afford that.
+1
Planning on updating this for v2
Currently FC uses the requested autoclick speed for time estimates, however this does not necessarily match the actual the real autoclick speed due to browser limitations. If I write
this shows:
Adding a
realcookieClickSpeed
function would make the time estimates much more accurate (and perhaps make purchasing calculations more precise).