I've redded out what you are wrong about.
Enzo1997 wrote:
Worthless Blocks are ever so easy to find...
Motion:
Turn 15 Degrees ()
Turn 15 Degrees ()
Go To []
Change x by ()
Change y by ()
Set x to ()
Set y to ()
If on edge bounce
Looks:
Next Costume
Change [] effect by ()
Change size by ()
Sound:
Change Volume by ()
Change Tempo by ()
Pen:
None
Control:
Repeat ()
Forever if <>
If <>
Wait Until <>
Stop Script
Stop All
Sensing:
Distance to []
[] of []
Those are IMPORTANT!
Offline
scimonster wrote:
I've redded out what you are wrong about.
Enzo1997 wrote:
Worthless Blocks are ever so easy to find...
Motion:
Turn 15 Degrees ()
Turn 15 Degrees ()
Go To []
Change x by ()
Change y by ()
Set x to ()
Set y to ()
If on edge bounce
Looks:
Next Costume
Change [] effect by ()
Change size by ()
Sound:
Change Volume by ()
Change Tempo by ()
Pen:
None
Control:
Repeat ()
Forever if <>
If <>
Wait Until <>
Stop Script
Stop All
Sensing:
Distance to []
[] of []Those are IMPORTANT!
I think what Enzo is trying to say is that the blocks he listed are not strictly necessary for a particular purpose (therefore in some way duplicates) but make programming easier. But I think he messed up the motion blocks... the direction seems pretty important to me!!
EDIT never mind... i forgot about the point in direction () block!
Last edited by LS97 (2011-02-07 16:10:03)
Offline
BoltBait wrote:
This block causes so much confusion, it should be removed from Scratch.
I see lots of projects that misuse this block thinking it is a Repeat Until block.
Seriously, just remove it.
Yeah. I agree to because you could just do this:
<forever><if>
Offline
No. Way. I mean, people can live with a little experiance, and it's been used in soooo many projects. It increases time to make the other forever block, and a lot of people use the forever block a lot of times. Plus, most newbies don't know even how to make a forever block anyway. Come on! We NEED that block!
BLEH LOOK BELOW!
Last edited by geohendan (2011-02-07 20:08:39)
Offline
geohendan wrote:
No. Way. I mean, people can live with a little experiance, and it's been used in soooo many projects. It increases time to make the other forever block, and a lot of people use the forever block a lot of times. Plus, most newbies don't know even how to make a forever block anyway. Come on! We NEED that block!
Oh, hey, are we talking about the forever IF block? Heh, heh... Missed the if... forget what I said... =_=
Offline
Well, I don't care if it stays in or not. I'm a frequent <Forever> <If> person and never used the <Forever if> block in my life. (Probably.) But if other people use it, I guess it should stay on.
Offline
Right now, on the Scratch stats on blocks, it says that 223315 projects use foreverIf_, while 930455 projects use forever and 418006 use if_.
Last edited by scimonster (2011-02-08 09:26:40)
Offline
I disagree to deleting the forever if block.
it will waste time deleting it.
Just don't use it.
Offline
2345lollly wrote:
I disagree to deleting the forever if block.
it will waste time deleting it.
Just don't use it.
They are already remaking the entire scratch for 2.0. It wouldn't have hurt them to make it obsolete, but they said no.
Offline
BoltBait wrote:
This block causes so much confusion, it should be removed from Scratch.
I see lots of projects that misuse this block thinking it is a Repeat Until block.
Seriously, just remove it.
Yeh but its easier than using ... <forever> and <if>
Offline
The-Critic wrote:
enzo i disagree with more than 80% of those. I use forever if and if all the time. everything with change x,y or ste x,y i use. go to and if on edge bounce help with games that need to have things randomly move liek dodgeing games as well asturning helps with those games. repeat, wait until, and stop script are alway helpful. All of those might not be important to you bcause ive seen some of your games that are really good, but to other scratchers like me, we use them all the time.
Can you give me ones you can't find a workaround to? That would be helpful, considering I can tell you the workaround
Offline
ah no one really cares. there is room on scratch for all of the blocks they have now and then some. some people use forever if and some people use a forever block, then an iff block. It truly makes no differnce, just deciding how many scripts u need to tell you the truth. I'll use either if I have to. If people use them wrong, they use them how they use hem. Let them do as they please. Stop telling them because seriously no one tells YOU how to do everything.
Thannk you and Scratch ON!!
Offline
They need to obsoletefy it. (I like the new word)
Offline
I will bold the ones i agree with
Enzo1997 wrote:
Worthless Blocks are ever so easy to find...
Motion:
Turn 15 Degrees () Whichever one, one should be taken off
Turn 15 Degrees ()
Go To []
Change x by ()
Change y by ()
Set x to ()
Set y to ()
If on edge bounce
Looks:
Next Costume This should only be taken off if they un-obsoletefy the change costume by block. Though you are right, it can be done without
Change [] effect by () That is the only way to do it unless you use variables :P
Change size by ()
Sound:
Change Volume by ()
Change Tempo by ()
Pen:
None
Control:
Repeat ()
Forever if <>
If <>
Wait Until <> Although you can use the repeat until block, this is a space saver
Stop Script
Stop All
Sensing:
Distance to []
[] of []
Offline
I will bold the ones that COULD be taken off.
Enzo1997 wrote:
Worthless Blocks are ever so easy to find...
Motion:
Turn 15 Degrees ()
Turn 15 Degrees ()
Go To []
Change x by ()
Change y by ()
Set x to ()
Set y to ()
If on edge bounce
Looks:
Next Costume
Change [] effect by
Change size by ()
Sound:
Change Volume by ()
Change Tempo by ()
Pen:
Control:
Repeat () Where did you get that idea?
Forever if <>
If <> Only if they kept the if else block, which is more useful than this one
Wait Until <>
Stop Script
Stop All
Sensing:
Distance to [] If the []of[] block was taken off you would need variables
[] of [] Only because of variables.
Last edited by Pecola1 (2011-05-03 14:02:55)
Offline
Maybe...
Offline
Even though some of you might think that <forever if><end> is useless and <forever><wait until><end> and <forever><end><if><end> just do the same. But <forever if><end> will stop doing what it's doing even if it's in the middle of it whilst <forever><wait until><end> and <forever><if><end> will only check when it's finished... =O
Offline
Yeah, get rid of it. It is so confusing. I used to think it was the same as <wait until><forever> and I would commit it as "FOREVER!!! Only if.......... I am uncomfortable with using it. It it can replaced with forever, inside if, so get rid of it! Plus it's not needed so if you delete it it won't take up so much space.
Offline
Zangoose2 wrote:
Even though some of you might think that <forever if><end> is useless and <forever><wait until><end> and <forever><end><if><end> just do the same. But <forever if><end> will stop doing what it's doing even if it's in the middle of it whilst <forever><wait until><end> and <forever><if><end> will only check when it's finished... =O[/blocks]
Really? I thought it only checked when it reached the top.
Offline
Woah.... I thought this topic was long gone.
Anyways, The Forever If block would be helpful if it weren't so confusing to new Scratchers.
Since it's a combo of 2 blocks, wouldn't it be easier to drag 2 blocks together instead of putting out a misleading title?
Offline
I've looked at the pros and cons and the pros really outway the cons. I now support!
Offline
i say keep it!
Offline
I know the difference... I worked it out one day... something to do with how they are exected... but I forgot...
Offline