Ok, ok, now, I don't think a New Scratcher will understand

when green flag clicked
forever
    ...
wait (pick random (... :: grey) to (... :: grey)) secs
end

Or

when green flag clicked
forever
    
if <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)> then
    ...
wait until <not <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)>>
end

end

Not if it's too complicated. That's why I think we should have these:

during a random moment :: events hat
when it's ():():() [AM v] :: events hat
(current [time v])

They're a lot simpler

Time doesn't use AM/PM system, it's military

Diamond_Projects wrote:

when it's ():():() [AM v] :: events hat

One problem. Time zones.
EDIT: And military time, thanks for the ninja, DemCupcakesYo.

TheHockeyist wrote:

Diamond_Projects wrote:

when it's ():():() [AM v] :: events hat

One problem. Time zones.
EDIT: And military time, thanks for the ninja, DemCupcakesYo.

(current [ v])

One problem. Time zones.

DemCupcakesYo wrote:

Time doesn't use AM/PM system, it's military

What do you mean?

Diamond_Projects wrote:

DemCupcakesYo wrote:

Time doesn't use AM/PM system, it's military

What do you mean?

The time block uses a 24 hour clock system. Instead of saying 1:00 PM, it would say 13:00.

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

djdolphin wrote:

Diamond_Projects wrote:

DemCupcakesYo wrote:

Time doesn't use AM/PM system, it's military

What do you mean?

The time block uses a 24 hour clock system. Instead of saying 1:00 PM, it would say 13:00.

Well, I knew THAT.

Diamond_Projects wrote:

Ok, ok, now, I don't think a New Scratcher will understand

when green flag clicked
forever
    ...
wait (pick random (... :: grey) to (... :: grey)) secs
end

Or

when green flag clicked
forever
    
if <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)> then
    ...
wait until <not <(join (join (join (join (current [hour v]) [:]) (current [minute v])) [:]) (current [second v])) = (time :: grey)>>
end

end

Not if it's too complicated. That's why I think we should have these:

during a random moment :: events hat
when it's ():():() [AM v] :: events hat
(current [time v])

They're a lot simpler

It's not really all that complicated. In terms of complexity, it's at most around the level of doing arithmetic with multiple-digit numbers. It's just mindlessly following an easy step-by-step process that pretty much everyone over the age of 5 should know how to do, but gives off the illusion of complexity because people find it hard to grasp the difference between “tedious” and “difficult”. If someone can't figure out something as straightforward as that, then s/he needs to develop the critical thinking skills to do so. Programming, whether in Scratch or any other language, is all about this stuff, from top to bottom.

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

You never said that for

(current [ v])

How is

when it's ():():() [AM v] :: events hat

different?

TheHockeyist wrote:

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

Scratch is presumably based somewhere in Massachusetts, so it's easier for them to use the New York time zone.

lalala3 wrote:

TheHockeyist wrote:

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

Scratch is presumably based somewhere in Massachusetts, so it's easier for them to use the New York time zone.

It's not like the block is cloud or anything.

Diamond_Projects wrote:

lalala3 wrote:

TheHockeyist wrote:

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

Scratch is presumably based somewhere in Massachusetts, so it's easier for them to use the New York time zone.

It's not like the block is cloud or anything.

That's also true, but that, as others have said, brings up the problem of time zones.

lalala3 wrote:

Diamond_Projects wrote:

lalala3 wrote:

TheHockeyist wrote:

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

Scratch is presumably based somewhere in Massachusetts, so it's easier for them to use the New York time zone.

It's not like the block is cloud or anything.

That's also true, but that, as others have said, brings up the problem of time zones.

Why?

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

lalala3 wrote:

TheHockeyist wrote:

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

Scratch is presumably based somewhere in Massachusetts, so it's easier for them to use the New York time zone.

It's not like the block is cloud or anything.

That's also true, but that, as others have said, brings up the problem of time zones.

Why?

Because if you want to set it to do something at a set time, you'd have to use a time zone converter to set it to Massachusetts time. But newer scratchers wouldn't know that, and it could easily get very confusing.

helloyowuzzup wrote:

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

lalala3 wrote:

TheHockeyist wrote:

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

Scratch is presumably based somewhere in Massachusetts, so it's easier for them to use the New York time zone.

It's not like the block is cloud or anything.

That's also true, but that, as others have said, brings up the problem of time zones.

Why?

Because if you want to set it to do something at a set time, you'd have to use a time zone converter to set it to Massachusetts time. But newer scratchers wouldn't know that, and it could easily get very confusing.

Or whatever your project's time zone is, not necessarily Eastern time.

helloyowuzzup wrote:

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

lalala3 wrote:

TheHockeyist wrote:

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

Scratch is presumably based somewhere in Massachusetts, so it's easier for them to use the New York time zone.

It's not like the block is cloud or anything.

That's also true, but that, as others have said, brings up the problem of time zones.

Why?

Because if you want to set it to do something at a set time, you'd have to use a time zone converter to set it to Massachusetts time. But newer scratchers wouldn't know that, and it could easily get very confusing.

No you won't. What's the point of doing that anyway? Besides, that's not the ONLY thing the block does.

Diamond_Projects wrote:

helloyowuzzup wrote:

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

lalala3 wrote:

TheHockeyist wrote:

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

Scratch is presumably based somewhere in Massachusetts, so it's easier for them to use the New York time zone.

It's not like the block is cloud or anything.

That's also true, but that, as others have said, brings up the problem of time zones.

Why?

Because if you want to set it to do something at a set time, you'd have to use a time zone converter to set it to Massachusetts time. But newer scratchers wouldn't know that, and it could easily get very confusing.

No you won't. What's the point of doing that anyway? Besides, that's not the ONLY thing the block does.

Well, what if I want to make a time-limited cloud poll? Maybe if I want to code a special event into a game or something? A timer counting down until something important happens?

lalala3 wrote:

Diamond_Projects wrote:

helloyowuzzup wrote:

Diamond_Projects wrote:

lalala3 wrote:

Diamond_Projects wrote:

lalala3 wrote:

TheHockeyist wrote:

helloyowuzzup wrote:

As someone pointed out, time zones would be a huge problem. I've suggested having a ‘Scratch time’ with a clock before, but people didn't like the idea ST says that they generally use the New York time zone for most things.
Anyway, tuba for the other block

I don't like the idea of Scratch time. I prefer UTC time.

Scratch is presumably based somewhere in Massachusetts, so it's easier for them to use the New York time zone.

It's not like the block is cloud or anything.

That's also true, but that, as others have said, brings up the problem of time zones.

Why?

Because if you want to set it to do something at a set time, you'd have to use a time zone converter to set it to Massachusetts time. But newer scratchers wouldn't know that, and it could easily get very confusing.

No you won't. What's the point of doing that anyway? Besides, that's not the ONLY thing the block does.

Well, what if I want to make a time-limited cloud poll? Maybe if I want to code a special event into a game or something? A timer counting down until something important happens?

You can use a cloud variable.