plasmaticatt wrote:

So, I'm trying to make a game where when you tap space while, say, examplesprite1 is touching examplesprite2, you get a point. If you press the button at any other time, you lose a point, and if you miss you also lose a point. The thing I'm worried about is, you can just hold down space; and even if you don't mean to, missing the spacebar key will result you in losing 7 points because it technically counted as holding it down. So, you lose a couple million points by holding down space bar. How do I set a cooldown? And while you're at it, can you guys tell me how to make a cooldown for clicking, too? Thanks.

wait until <not <key [space v] pressed?>>

blablablahello wrote:

plasmaticatt wrote:

So, I'm trying to make a game where when you tap space while, say, examplesprite1 is touching examplesprite2, you get a point. If you press the button at any other time, you lose a point, and if you miss you also lose a point. The thing I'm worried about is, you can just hold down space; and even if you don't mean to, missing the spacebar key will result you in losing 7 points because it technically counted as holding it down. So, you lose a couple million points by holding down space bar. How do I set a cooldown? And while you're at it, can you guys tell me how to make a cooldown for clicking, too? Thanks.

add a

wait until <not <key [space v] pressed?>>

when [space v] key pressed
change [points v] by (0)

when this sprite clicked
do stuff

plasmaticatt wrote:

Unfortunately, the “wait until” script freezes the entire game while space is held. The “when space key pressed” also has no effect on the issue.

forever
if <key [key v] pressed?> then
set [lastpress v] to ((days since 2000) * [86400])
wait until <<not <key [key v] pressed?>> or <(((days since 2000) * [86400]) - (lastpress)) < [Change this to how quick the cooldown should be]>>
if <key [key v] pressed?> then
Punish the player for holding down the key! 
end

plasmaticatt wrote:

Unfortunately, I really can't seem to get it; I think maybe sharing the project will help give you guys a better idea? https://scratch.mit.edu/projects/732538167/

plasmaticatt wrote:

Also just tried to do what you said, the only thing thats happening is the value of “lastpress” increasing

plasmaticatt wrote:

Also just tried to do what you said, the only thing thats happening is the value of “lastpress” increasing

<<not <key [space v] pressed?>> or <((days since 2000) * (86400)) < (lastpress)>>

<<not <key [space v] pressed?>> or <(((days since 2000) * (86400)) - (lastpress)) > [Cooldown]>>

DeveloperTools wrote:

plasmaticatt wrote:

Also just tried to do what you said, the only thing thats happening is the value of “lastpress” increasing

You put

<<not <key [space v] pressed?>> or <((days since 2000) * (86400)) < (lastpress)>>

Instead of:

<<not <key [space v] pressed?>> or <(((days since 2000) * (86400)) - (lastpress)) > [Cooldown]>>

plasmaticatt wrote:

Still isn't working.. I assume I have to define “lastpress,” but what exactly is it in the way you intend?

when green flag clicked
forever
go to x: (0) y: (200)
repeat until <<key [space v] pressed>or<out of bounds>>
falling script
end
if <touching [detector]> then
change [score v] by (1)
else
change [score v] by (-1)
end
repeat until <out of bounds>
falling script
end
wait (cooldown) secs

plasmaticatt wrote:

Still isn't working.. I assume I have to define “lastpress,” but what exactly is it in the way you intend?

<(((days since 2000) * [86400]) - (lastpress)) > [cooldown]> // HAS TO BE >, NOT < (my original reply had the wrong inequality)