Discuss Scratch
- supercroissants
-
New Scratcher
36 posts
more timer blocks
ever heard ofwe shouldn't have to make variables to use blocks as simple as theseforever
change [timer1 v] by (1)
wait (1) seconds
- NutOfCoco
-
Scratcher
100+ posts
more timer blocks
Sorry to break this to you, but a timer is a variable.ever heard ofwe shouldn't have to make variables to use blocks as simple as theseforever
change [timer1 v] by (1)
wait (1) seconds
- supercroissants
-
New Scratcher
36 posts
more timer blocks
sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would beSorry to break this to you, but a timer is a variable.ever heard ofwe shouldn't have to make variables to use blocks as simple as theseforever
change [timer1 v] by (1)
wait (1) seconds
you don't make it, you don't have to do anything to make it appear, it is a constant.
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer
if we removed every block that had a workaround nobody would use the site
- NutOfCoco
-
Scratcher
100+ posts
more timer blocks
Sorry to break it to you, but a constant is a variable that does not change, a timer's whole purpose is to change, and most people when giving a workaround are giving it to the person so that person can implement use the suggested block before the suggestion is added (or never).sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would beSorry to break this to you, but a timer is a variable.ever heard ofwe shouldn't have to make variables to use blocks as simple as theseforever
change [timer1 v] by (1)
wait (1) seconds
you don't make it, you don't have to do anything to make it appear, it is a constant.
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer
if we removed every block that had a workaround nobody would use the site
- supercroissants
-
New Scratcher
36 posts
more timer blocks
sorry to break it to you, I know that!Sorry to break it to you, but a constant is a variable that does not change, a timer's whole purpose is to change, and most people when giving a workaround are giving it to the person so that person can implement use the suggested block before the suggestion is added (or never).sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would beSorry to break this to you, but a timer is a variable.ever heard ofwe shouldn't have to make variables to use blocks as simple as theseforever
change [timer1 v] by (1)
wait (1) seconds
you don't make it, you don't have to do anything to make it appear, it is a constant
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer
if we removed every block that had a workaround nobody would use the site
I said constant in the sense that it will always be a thing in scratch projects.
and the message that we're all quoting is in a tone that suggests “hey, here's a workaround. this suggestion bad!”
workarounds and overprotective people will be the death of this forum
- r3hehehehehhe
-
Scratcher
1000+ posts
more timer blocks
sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would bei agree with you, it's like saying we don't need
you don't make it, you don't have to do anything to make it appear, it is a constant.
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer
if we removed every block that had a workaround nobody would use the site
<<boolean::grey> and <boolean::grey>>we can use
<<<boolean::grey> = [true]> = <<boolean::grey> = [true]>>
- NutOfCoco
-
Scratcher
100+ posts
more timer blocks
That workaround doesn't work, it is also true for two false values.sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would bei agree with you, it's like saying we don't need
you don't make it, you don't have to do anything to make it appear, it is a constant.
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer
if we removed every block that had a workaround nobody would use the site<<boolean::grey> and <boolean::grey>>we can use<<<boolean::grey> = [true]> = <<boolean::grey> = [true]>>
- robloxnoob27
-
New Scratcher
100+ posts
more timer blocks
That workaround doesn't work, it is also true for two false values.sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would bei agree with you, it's like saying we don't need
you don't make it, you don't have to do anything to make it appear, it is a constant.
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer
if we removed every block that had a workaround nobody would use the site<<boolean::grey> and <boolean::grey>>we can use<<<boolean::grey> = [true]> = <<boolean::grey> = [true]>>
<not <<not <boolean::grey>> or <not <boolean::grey>>>
- NutOfCoco
-
Scratcher
100+ posts
more timer blocks
What about mine?and the message that we're all quoting is in a tone that suggests “hey, here's a workaround. this suggestion bad!”Sorry to break it to you, but a constant is a variable that does not change, a timer's whole purpose is to change, and most people when giving a workaround are giving it to the person so that person can implement use the suggested block before the suggestion is added (or never).sorry to break it to you, the timer isn't a variable in the same way something like "my variable' would beSorry to break this to you, but a timer is a variable.ever heard ofwe shouldn't have to make variables to use blocks as simple as theseforever
change [timer1 v] by (1)
wait (1) seconds
you don't make it, you don't have to do anything to make it appear, it is a constant
it would be a lot easier to just keep it that way and add a couple of blocks improving the timer
if we removed every block that had a workaround nobody would use the site
Last edited by NutOfCoco (Today 04:43:00)
- robloxnoob27
-
New Scratcher
100+ posts
more timer blocks
17 block workaround:
define timer (type) (start time)
set [timer v] to (start time)
reset timer
repeat until <(timer::variables) < [0]>
set [timer v] to ((start time)-((((2)*<(type)=[countdown]>)-[1])*(timer)))
end
set [timer v] to [0]