Scratch

zawicki1fromyoutube · 2008-12-09 17:22:25

I have ALOT.

Control Blocks:

When "Back Space" key pressed and any other key besides stuff like f1-f12 and stuff. just letters, shift,backspace, numbers, shift+key, and enter.

Broadcast For (?) seconds: This will ony make the broadcast work for all sprites for a certain amount of time.

Stop Scripts () to (): This allows you to stop certain scripts. Also, for this, I think there should be an "Auto-matic" counter, and it would count the exact order highest to lowest.

Motion:

If touching [ ] bounce

Point Away From [ ]

Point Towards x:( ) y: ( )

Variables:

Hide/Show Lists

UPDATE for variables: Hide/Show for lists and variables work online.

Number:
<( ) =,<,> ( )> fits words.

Sensing:

If touching Section of [ ]

More to Come Soon...

Last edited by zawicki1fromyoutube (2008-12-09 17:23:09)

boinoinoi · 2008-12-09 21:44:22

Let's see how many ones I can deny... hmm...

-1. Broadcast for [ ] secs
this can be done quite easily with variables.

-2. If touching [ ] bounce
you have no idea what angle the surface you're bouncing off is.

-3. Point away from [ ]
point toward [ ]
turn (either way) 180

-4. touching section of [ ]
What sections? and plus you can just make several sensor sprites for each section.

AND BEFORE ANYONE SUGGESTS IT, WAIT UNTIL I RECIEVE OR WHATEVER IS IMPOSSIBLE

And what is your numbers suggestion? it make 0 sense

bhz · 2008-12-10 06:18:09

boinoinoi wrote:
-2. If touching [ ] bounce
you have no idea what angle the surface you're bouncing off is.

That's why we need a block for it

boinoinoi · 2008-12-10 16:17:39

bhz wrote:
boinoinoi wrote:
-2. If touching [ ] bounce
you have no idea what angle the surface you're bouncing off is.
That's why we need a block for it

No, that's why it's impossible. Because NO ONE knows what angle it is. Unless it's a circle, in which case you can make some scripts for that.

HungryDragon · 2008-12-10 17:23:19

I have a suggestion. Have Scratch be able to sent and get broadcasts and data from other projects for muiltiplayer games.

zawicki1fromyoutube · 2008-12-10 18:10:04

boinoinoi wrote:
Let's see how many ones I can deny... hmm...

-1. Broadcast for [ ] secs
this can be done quite easily with variables.

-2. If touching [ ] bounce
you have no idea what angle the surface you're bouncing off is.

-3. Point away from [ ]
point toward [ ]
turn (either way) 180

-4. touching section of [ ]
What sections? and plus you can just make several sensor sprites for each section.

AND BEFORE ANYONE SUGGESTS IT, WAIT UNTIL I RECIEVE OR WHATEVER IS IMPOSSIBLE

And what is your numbers suggestion? it make 0 sense

THESE ALL MAKE SENSE, AND ALL JUST MAKE SCRATCH EASIER. And also, for your your information, "I receive" IS POSSIBLE. A <> block is a boolean. A Boolean says "TRUE" or "FALSE".IT DOES WORK. If you put into a "say" block, it would say "Ture" if you received it, and "False" if it was not broadcasted. PWND! lol XD

zawicki1fromyoutube · 2008-12-10 18:11:20

boinoinoi wrote:
bhz wrote:
boinoinoi wrote:
-2. If touching [ ] bounce
you have no idea what angle the surface you're bouncing off is.
That's why we need a block for it
No, that's why it's impossible. Because NO ONE knows what angle it is. Unless it's a circle, in which case you can make some scripts for that.

Yes you do. Just look at the "direction". Scratch cna determine directions. It IS possible. Proved AGAIN.

keroro645 · 2008-12-10 18:14:38

I dont know how a "" is not boolean.

zawicki1fromyoutube · 2008-12-10 18:31:09

keroro645 wrote:
I dont know how a "" is not boolean.

FIANLLY SOMEONE AGREES.

bhz · 2008-12-10 20:00:33

keroro645 wrote:
I dont know how a "" is not boolean.

it is boolean. But the about of time something is recieved is so little it's basically like doing this in a script:

<set{ broadcasting }to( 1
<set{ broadcasting }to( 0 [/blocks]

 is surely possible. But that can be done with variables:

Stage:
<when green flag clicked>
<set{ received }to( 0

<when I receive[ message
<set{ received }to( 1 [/blocks]

Where block WOULD be placed
<( <{ received }> <=> 1 )>[/blocks]

Last edited by bhz (2008-12-10 20:00:54)

boinoinoi · 2008-12-11 16:42:43

zawicki1fromyoutube wrote:
boinoinoi wrote:
bhz wrote:

That's why we need a block for it
No, that's why it's impossible. Because NO ONE knows what angle it is. Unless it's a circle, in which case you can make some scripts for that.
Yes you do. Just look at the "direction". Scratch cna determine directions. It IS possible. Proved AGAIN.

NO.

What I mean is that if something is bouncing off of an irregular shape, the angle of the plane it is bouncing off of has nothing to do with what direction anything is pointing. You can only tell what direction the sprites are pointing, and no data besides color and whether or not a sprite is touching another one. The angle of the lines in the costume cannot be determined by pretty much anything just in scratch.

BURN.

zawicki1fromyoutube · 2008-12-11 16:49:20

boinoinoi wrote:
zawicki1fromyoutube wrote:
boinoinoi wrote:

No, that's why it's impossible. Because NO ONE knows what angle it is. Unless it's a circle, in which case you can make some scripts for that.
Yes you do. Just look at the "direction". Scratch cna determine directions. It IS possible. Proved AGAIN.
NO.

What I mean is that if something is bouncing off of an irregular shape, the angle of the plane it is bouncing off of has nothing to do with what direction anything is pointing. You can only tell what direction the sprites are pointing, and no data besides color and whether or not a sprite is touching another one. The angle of the lines in the costume cannot be determined by pretty much anything just in scratch.

BURN.

Okay. then I'll add something to my list. tongue The ability to make lines in a costum "opint" in a certain direction.

BURNED. Hot like a stove! Watch me move! lol Need an Ice pack?

BWOG · 2008-12-12 10:40:44

boinoinoi wrote:
zawicki1fromyoutube wrote:
boinoinoi wrote:

No, that's why it's impossible. Because NO ONE knows what angle it is. Unless it's a circle, in which case you can make some scripts for that.
Yes you do. Just look at the "direction". Scratch cna determine directions. It IS possible. Proved AGAIN.
NO.

What I mean is that if something is bouncing off of an irregular shape, the angle of the plane it is bouncing off of has nothing to do with what direction anything is pointing. You can only tell what direction the sprites are pointing, and no data besides color and whether or not a sprite is touching another one. The angle of the lines in the costume cannot be determined by pretty much anything just in scratch.

BURN.

This isn't supposed to be a fight! all the block should be is do the same thing as <if touching [Sprite1 V]> Turn 180 degrees!

JSO · 2008-12-12 10:52:02

Maybe the bounce off [] block is possible.

I only have no idea how long it would take to execute, and ofcourse, a block has to be executed quickly.

Some of them are useful (I like the point towards x: y: !) Others can easily be done with the blocks we already have.

Please, don't start a fight because you don't like a suggestion someone else made...

boinoinoi · 2008-12-13 18:32:26

BWOG wrote:
boinoinoi wrote:
zawicki1fromyoutube wrote:

Yes you do. Just look at the "direction". Scratch cna determine directions. It IS possible. Proved AGAIN.
NO.

What I mean is that if something is bouncing off of an irregular shape, the angle of the plane it is bouncing off of has nothing to do with what direction anything is pointing. You can only tell what direction the sprites are pointing, and no data besides color and whether or not a sprite is touching another one. The angle of the lines in the costume cannot be determined by pretty much anything just in scratch.

BURN.
This isn't supposed to be a fight! all the block should be is do the same thing as <if touching [Sprite1 V]> Turn 180 degrees!

I am not making a fight. zawiki was just being stubborn about his opinion.

And still is.

And @ zawiki: what about when you use the pencil tool? or import costumes? or use anything beside the line tool?

I suppose you now need to take an aloe bath...

Roberth · 2008-12-13 21:51:59

One idea that is long overdue for Scratch and hasn't been explained away effectively:

String Variables

I really don't understand why these aren't in the system, and there are so many legitimate applications where they could be useful. Being able to "stuff" strings into textual images (aka be able to "render" a string on screen) would be a part of that.

IMHO, string variables ought to have a decidedly different shape from numeric variables... such as a pentagon or a hard square. Certainly something distinctive but in keeping with the language.

Some string operators could be implemented too, including concatenation operators (merge <string> onto <string>), substrings (extract from <string> starting at <number> to <number>), and comparitors (is <string> equal to <string>?) Yeah, this could be cleaned up in terms of grammar, but it isn't over the top. This is the #1 thing missing from Scratch that appears in Dartmouth BASIC.

tharvoil · 2008-12-13 22:40:04

boinoinoi wrote:
If touching [ ] bounce
you have no idea what angle the surface you're bouncing off is.

I Beleive I can help with this, its quite simple how the if on edge bounce works.

Basicly what that block does is whatever direction your going in when you hit the edge lets say 76 is ur direction, once you bounce youll face -76.

If it was 90 it would become -90 after bouncing

If it was -39.2 it would become 39.2 after bouncing, very simple and heres teh script you can use to prove it:

<when green flag clicked>
<point in direction( 90)
<turn cw( 0 )degrees> - change to set the angle
<forever>
<move( 10 )steps>
<if on edge, bounce>

Like i said very easy to figure out just use the basic sprite and check the box to tell you what the direction is.

ferret10 · 2008-12-20 22:46:54

i definitly want to see some kind of "when [] received" block that can go inside another script.

ScratchScripter · 2008-12-23 12:03:58

zawicki1fromyoutube wrote:
boinoinoi wrote:
Let's see how many ones I can deny... hmm...

-1. Broadcast for [ ] secs
this can be done quite easily with variables.

-2. If touching [ ] bounce
you have no idea what angle the surface you're bouncing off is.

-3. Point away from [ ]
point toward [ ]
turn (either way) 180

-4. touching section of [ ]
What sections? and plus you can just make several sensor sprites for each section.

AND BEFORE ANYONE SUGGESTS IT, WAIT UNTIL I RECIEVE OR WHATEVER IS IMPOSSIBLE

And what is your numbers suggestion? it make 0 sense
THESE ALL MAKE SENSE, AND ALL JUST MAKE SCRATCH EASIER. And also, for your your information, "I receive" IS POSSIBLE. A <> block is a boolean. A Boolean says "TRUE" or "FALSE".IT DOES WORK. If you put into a "say" block, it would say "Ture" if you received it, and "False" if it was not broadcasted. PWND! lol XD

I also really need this block, but the Scratch Team already said it's impossible, you can ask them...
You'll need to make variables for each object to make something similar work.

What COULD be possible is a newly shaped block that is active until it is "used".
E.g.:
[ repeat until { recieved [ message ] } ]
-Blocks-
[ ]

boinoinoi · 2008-12-23 21:29:34

zawicki1fromyoutube wrote:
THESE ALL MAKE SENSE, AND ALL JUST MAKE SCRATCH EASIER. And also, for your your information, "I receive" IS POSSIBLE. A <> block is a boolean. A Boolean says "TRUE" or "FALSE".IT DOES WORK. If you put into a "say" block, it would say "Ture" if you received it, and "False" if it was not broadcasted. PWND! lol XD

I just realized, this post makes no sense.

Let's break it down:

THESE ALL MAKE SENSE, AND ALL JUST MAKE SCRATCH EASIER.

I only said that your math suggestion made no sense: It's a bunch of symbols with "fits words" slapped on the back. Also, easier, maybe but slower definitely.

And also, for your your information, "I receive" IS POSSIBLE.

Why don't you explain that, then.

A <> block is a boolean.

True.

A Boolean says "TRUE" or "FALSE".

True as well.

IT DOES WORK.

You stated blatant facts that don't prove anything. Or are you just being redundant for no reason?

If you put into a "say" block, it would say "Ture" if you received it, and "False" if it was not broadcasted.

Wait,
wait,
wait
wait
wait

wait.
You wanted something you can already do? Well guess what? Chances are the scratch team developers are probably not going to make a whole new block just so you can do something you can ALREADY DO IN SCRATCH without prior math knowledge or anything. Don't believe me? HERE:

When I receive [broadcast]
change [ variable ] by ( 1 )

When Green Flag pressed
set [ variable ] to ( 0 )

and your "when I receive" block is:
< ( variable ) > ( 0 ) >

Ta-da.
Two scripts
Four blocks

Is it really that hard to do it yourself?

And use proper grammar. And spelling. That always annoys me.

the_employee · 2008-12-29 19:41:55

boinoinoi wrote:
zawicki1fromyoutube wrote:
THESE ALL MAKE SENSE, AND ALL JUST MAKE SCRATCH EASIER. And also, for your your information, "I receive" IS POSSIBLE. A <> block is a boolean. A Boolean says "TRUE" or "FALSE".IT DOES WORK. If you put into a "say" block, it would say "Ture" if you received it, and "False" if it was not broadcasted. PWND! lol XD
I just realized, this post makes no sense.

Let's break it down:

THESE ALL MAKE SENSE, AND ALL JUST MAKE SCRATCH EASIER.
I only said that your math suggestion made no sense: It's a bunch of symbols with "fits words" slapped on the back. Also, easier, maybe but slower definitely.

And also, for your your information, "I receive" IS POSSIBLE.
Why don't you explain that, then.

A <> block is a boolean.
True.

A Boolean says "TRUE" or "FALSE".
Frankly, I do not (and cannot) agree with you, for the reason that you are practically insulting people. The Scratch Team can decide upon others ideas, and they can tell you if its possible or not. You cannot judge others ideas when they're only thinking about possibilities, ever heard about Albert Einstein? I don't think you're part of the Scratch Team...
True as well.

IT DOES WORK.
You stated blatant facts that don't prove anything. Or are you just being redundant for no reason?

If you put into a "say" block, it would say "Ture" if you received it, and "False" if it was not broadcasted.
Wait,
wait,
wait
wait
wait

wait.
You wanted something you can already do? Well guess what? Chances are the scratch team developers are probably not going to make a whole new block just so you can do something you can ALREADY DO IN SCRATCH without prior math knowledge or anything. Don't believe me? HERE:

When I receive [broadcast]
change [ variable ] by ( 1 )

When Green Flag pressed
set [ variable ] to ( 0 )

and your "when I receive" block is:
< ( variable ) > ( 0 ) >

Ta-da.
Two scripts
Four blocks

Is it really that hard to do it yourself?

And use proper grammar. And spelling. That always annoys me.

boinoinoi · 2008-12-29 20:08:25

the_employee wrote:
boinoinoi wrote:
[...]

What was the point of that?

illusionist · 2009-02-11 20:16:58

zawicki1fromyoutube wrote:
I have ALOT.

Control Blocks:

When "Back Space" key pressed and any other key besides stuff like f1-f12 and stuff. just letters, shift,backspace, numbers, shift+key, and enter.

Broadcast For (?) seconds: This will ony make the broadcast work for all sprites for a certain amount of time.

Stop Scripts () to (): This allows you to stop certain scripts. Also, for this, I think there should be an "Auto-matic" counter, and it would count the exact order highest to lowest.

Motion:

If touching [ ] bounce

Point Away From [ ]

Point Towards x ) y: ( )

Variables:

Hide/Show Lists

UPDATE for variables: Hide/Show for lists and variables work online.

Number:
<( ) =,<,> ( )> fits words.

Sensing:

If touching Section of [ ]

More to Come Soon...

The 'point away from [ ]' and 'point towards x: ( ) y: ( )' are already possible.

And the Enter key starts the green *.

techy · 2009-02-11 20:36:51

illusionist wrote:
zawicki1fromyoutube wrote:
I have ALOT.

Control Blocks:

When "Back Space" key pressed and any other key besides stuff like f1-f12 and stuff. just letters, shift,backspace, numbers, shift+key, and enter.

Broadcast For (?) seconds: This will ony make the broadcast work for all sprites for a certain amount of time.

Stop Scripts () to (): This allows you to stop certain scripts. Also, for this, I think there should be an "Auto-matic" counter, and it would count the exact order highest to lowest.

Motion:

If touching [ ] bounce

Point Away From [ ]

Point Towards x ) y: ( )

Variables:

Hide/Show Lists

UPDATE for variables: Hide/Show for lists and variables work online.

Number:
<( ) =,<,> ( )> fits words.

Sensing:

If touching Section of [ ]

More to Come Soon...
The 'point away from [ ]' and 'point towards x: ( ) y: ( )' are already possible.

And the Enter key starts the green *.

well he could just make a hidden sprite(by using the hide block) and make it so it goes
to what ever x ,y and for the visible sprite put point towards sprite(hidden sprite name)

Hope that wasnt to confusing....

-Techy big_smile

BWOG · 2009-02-12 08:32:48

boinoinoi wrote:
zawicki1fromyoutube wrote:
THESE ALL MAKE SENSE, AND ALL JUST MAKE SCRATCH EASIER. And also, for your your information, "I receive" IS POSSIBLE. A <> block is a boolean. A Boolean says "TRUE" or "FALSE".IT DOES WORK. If you put into a "say" block, it would say "Ture" if you received it, and "False" if it was not broadcasted. PWND! lol XD
I just realized, this post makes no sense.

If you put into a "say" block, it would say "Ture" if you received it, and "False" if it was not broadcasted.
Wait,
wait,
wait
wait
wait

wait.
You wanted something you can already do? Well guess what? Chances are the scratch team developers are probably not going to make a whole new block just so you can do something you can ALREADY DO IN SCRATCH without prior math knowledge or anything. Don't believe me? HERE:

When I receive [broadcast]
change [ variable ] by ( 1 )

When Green Flag pressed
set [ variable ] to ( 0 )

and your "when I receive" block is:
< ( variable ) > ( 0 ) >

Ta-da.
Two scripts
Four blocks

Is it really that hard to do it yourself?

And use proper grammar. And spelling. That always annoys me.

Oh, so we should get rid of ethier the <turn cw( )degrees> block or the <turn cw( )degrees> block since all you have to do is make the sprite turn more in one direction and the if on edge bounce because you can do <touching[ edge turn 180 degrees

Scratch

archived forums

#1 2008-12-09 17:22:25

Scratch 1.4 Suggestions

#2 2008-12-09 21:44:22

Re: Scratch 1.4 Suggestions

#3 2008-12-10 06:18:09

Re: Scratch 1.4 Suggestions

boinoinoi wrote:

#4 2008-12-10 16:17:39

Re: Scratch 1.4 Suggestions

bhz wrote:

boinoinoi wrote:

#5 2008-12-10 17:23:19

Re: Scratch 1.4 Suggestions

#6 2008-12-10 18:10:04

Re: Scratch 1.4 Suggestions

boinoinoi wrote:

#7 2008-12-10 18:11:20

Re: Scratch 1.4 Suggestions

boinoinoi wrote:

bhz wrote:

boinoinoi wrote:

#8 2008-12-10 18:14:38

Re: Scratch 1.4 Suggestions

#9 2008-12-10 18:31:09

Re: Scratch 1.4 Suggestions

keroro645 wrote:

#10 2008-12-10 20:00:33

Re: Scratch 1.4 Suggestions

keroro645 wrote:

#11 2008-12-11 16:42:43

Re: Scratch 1.4 Suggestions

zawicki1fromyoutube wrote:

boinoinoi wrote:

bhz wrote:

#12 2008-12-11 16:49:20

Re: Scratch 1.4 Suggestions

boinoinoi wrote:

zawicki1fromyoutube wrote:

boinoinoi wrote:

#13 2008-12-12 10:40:44

Re: Scratch 1.4 Suggestions

boinoinoi wrote:

zawicki1fromyoutube wrote:

boinoinoi wrote:

#14 2008-12-12 10:52:02

Re: Scratch 1.4 Suggestions

#15 2008-12-13 18:32:26

Re: Scratch 1.4 Suggestions

BWOG wrote:

boinoinoi wrote:

zawicki1fromyoutube wrote:

#16 2008-12-13 21:51:59

Re: Scratch 1.4 Suggestions

#17 2008-12-13 22:40:04

Re: Scratch 1.4 Suggestions

boinoinoi wrote:

#18 2008-12-20 22:46:54

Re: Scratch 1.4 Suggestions

#19 2008-12-23 12:03:58

Re: Scratch 1.4 Suggestions

zawicki1fromyoutube wrote:

boinoinoi wrote:

#20 2008-12-23 21:29:34

Re: Scratch 1.4 Suggestions

zawicki1fromyoutube wrote:

#21 2008-12-29 19:41:55

Re: Scratch 1.4 Suggestions

boinoinoi wrote:

zawicki1fromyoutube wrote:

#22 2008-12-29 20:08:25

Re: Scratch 1.4 Suggestions

the_employee wrote:

boinoinoi wrote:

#23 2009-02-11 20:16:58

Re: Scratch 1.4 Suggestions

zawicki1fromyoutube wrote:

#24 2009-02-11 20:36:51

Re: Scratch 1.4 Suggestions