A boolean is a diamond shapped block, right? If that's true, than I need it. It's kinda hard to do the stuff I need to do without it
Last edited by steppenwulf (2010-08-14 11:03:24)
Offline
Paddle2See suggested this in Scratch Suggestions already - it's doing well, maybe it'll get approved.
But then again extra topics don't really hurt. xP
Offline
Chrischb wrote:
Paddle2See suggested this in Scratch Suggestions already - it's doing well, maybe it'll get approved.
But then again extra topics don't really hurt. xP
lol yes!
We do need one. It would seriously make making games a lot easier.
Offline
Including 1s1s projects.
But that takes some of the challenge out, taking part of the fun also.
Offline
You don't really need it- just use a variable, and if the thing is true, set it to 1, and remember to set it to 0 when you aren't using it.
Offline
I personally disagree with the idea.
Can you describe why you need it/ how it would extremely make things better? Because as I mentioned before on Scratch Suggestions:
Lucario621 wrote:
[...] broadcasts are events - not true or false statements. A big flaw with this is, a broadcast happens for less than a second; only for one frame, and thus, couldn't a script accidentally skip one the broadcast?
Overall, it would all of the time miss the broadcast. The way a broadcast works, is it just finds all of the hat blocks with the broadcast, and starts them - nothing else really.
Offline
Sunrise-Moon wrote:
You don't really need it- just use a variable, and if the thing is true, set it to 1, and remember to set it to 0 when you aren't using it.
Well I know that, but here's the thing. For the game I'm developing, I would need DOZENS of "if thing is true, set it to 1" variables. And I would need just as many scripts for each idividual one. I need a simple way to do all of this, so I can reduce lag.
@Lucario- Basically I need it to reduce lag. Because I would have to many "if thing is true blah blah blah" scripts floating around, making it extremely laggy.
And it would work because you could put a <I recieve [ ]> block inside of a "wait until" block so it would wait to get a certain broadcast to perform a certain action.
Last edited by steppenwulf (2010-08-14 23:07:59)
Offline
It should be called "() received", I guess - and that's what Paddle2See did in his suggestion.
Offline
steppenwulf wrote:
Sunrise-Moon wrote:
You don't really need it- just use a variable, and if the thing is true, set it to 1, and remember to set it to 0 when you aren't using it.
Well I know that, but here's the thing. For the game I'm developing, I would need DOZENS of "if thing is true, set it to 1" variables. And I would need just as many scripts for each idividual one. I need a simple way to do all of this, so I can reduce lag.
@Lucario- Basically I need it to reduce lag. Because I would have to many "if thing is true blah blah blah" scripts floating around, making it extremely laggy.
And it would work because you could put a <I recieve [ ]> block inside of a "wait until" block so it would wait to get a certain broadcast to perform a certain action.
Use a list.
Offline
Sunrise-Moon wrote:
steppenwulf wrote:
Sunrise-Moon wrote:
You don't really need it- just use a variable, and if the thing is true, set it to 1, and remember to set it to 0 when you aren't using it.
Well I know that, but here's the thing. For the game I'm developing, I would need DOZENS of "if thing is true, set it to 1" variables. And I would need just as many scripts for each idividual one. I need a simple way to do all of this, so I can reduce lag.
@Lucario- Basically I need it to reduce lag. Because I would have to many "if thing is true blah blah blah" scripts floating around, making it extremely laggy.
And it would work because you could put a <I recieve [ ]> block inside of a "wait until" block so it would wait to get a certain broadcast to perform a certain action.Use a list.
That's still to much scripting to be done I need a heavily simplified way to do what I need to be done, and "() received" would workk perfectly.
Offline
Sunrise-Moon wrote:
You don't really need it- just use a variable, and if the thing is true, set it to 1, and remember to set it to 0 when you aren't using it.
That would work, or use a list.
Offline
Maybe it would be a fun programming exercise to learn how to efficiently use those variables. Don't underestimate the power of programming
It takes away from the challenge of programming if every solution is handed to you on a silver platter
Offline
coolstuff wrote:
Maybe it would be a fun programming exercise to learn how to efficiently use those variables. Don't underestimate the power of programming
It takes away from the challenge of programming if every solution is handed to you on a silver platter
Agreed, but would you enjoy making a perfect calculator without lists?
Offline
Chrischb wrote:
coolstuff wrote:
Maybe it would be a fun programming exercise to learn how to efficiently use those variables. Don't underestimate the power of programming
It takes away from the challenge of programming if every solution is handed to you on a silver platterAgreed, but would you enjoy making a perfect calculator without lists?
I agree.
It's seriously a block that simplified quite a bit of unnecessary programming.
Offline
I think we would all like that block.
Offline
As an elaboration: my previous post, which if you don't remember was this:
me wrote:
Maybe it would be a fun programming exercise to learn how to efficiently use those variables. Don't underestimate the power of programming
It takes away from the challenge of programming if every solution is handed to you on a silver platter
didn't necessarily mean that I didn't support. I was just trying to get people's hopes up for the time being. Also, I never said anything about not using lists
Offline
It's in many mods, such as Slash, but it doesn't work very well.
Offline