ChildCritic wrote:

@theonlygusti:
How about you reread my ENTIRE post.
It provides you with exactly what you need.

TOTALLY NOT ChildCritic wrote:

Let's remove the move block as it has a workaround:

move (10) steps // we don't need this anymore


go to x: ((x position) + (([sin v] of (direction)) * (number))) y: ((y position) + (([cos v] of (direction)) * (number)) // much better

that same guy who is totally not me but claims to be wrote:

Let's also remove:

turn ccw () degrees
turn cw () degrees
point towards [ v]
go to [ v]
glide () secs to x: (0) y: (0)
change x by ()
set x to ()
change y by ()
set y to ()
if on edge, bounce
(x position)
(y position)
say [] for (2) secs
think [] for (2) secs
think []
say []
next costume
switch backdrop to [ v]
change [ v] effect by (25)
clear graphic effects
change size by ()
go to front
(costume #)
(size)
switch backdrop to [ v] and wait
next backdrop
play sound [ v] until done
set volume to (volume) %
set tempo to () bpm
set pen color to ()
set pen shade to ()
set pen size to ()

when [ v] key pressed

when this sprite clicked

when backdrop switches to [ v]

when I receive [ v]
broadcast [ v]
broadcast [ v] and wait
wait () secs
repeat ()
forever
    
wait until <touching color [#ff0088] ?>
(timer)
reset timer
([(() - (0)) v] of [  v])
set [ v] to [ ]
add [] to [  v]
replace item ( v) of [  v] with [ ]
<[ v] contains [ ]>
    (length of [ v])
(distance to [ v])
(length of [])
(letter () of [world])
(join [] [world])
<<> or <>>
(() * (0))
(pick random (1) to (10)
<[] = [ ]>

and the entire custom block section!

theonlygusti wrote:

ChildCritic wrote:

@theonlygusti:
How about you reread my ENTIRE post.
It provides you with exactly what you need.

Erm, I don't see it.

ChildCritic wrote:

Okay. Let's do this thoroughly.
This works if a clone's parent is a clone.
Just add before the cloning:

set [saveparent v] to (parent)//local
set [parent v] to (Clone number)//also local
create clone of [myself v]
set [parent v] to (saveparent)

This works if the parent is not a clone

pvz_pro wrote:

@ChildCritic
the term “parent” is commonly used in programing and it is not used anywhere in scratch

Ninkancho wrote:

I think the parent would be the stage. But what would the stage's parent be?

Jonathan50 wrote:

Full support.

Ninkancho wrote:

I think the parent would be the stage. But what would the stage's parent be?

The stage shouldn't have a parent. The option shouldn't show in the stage and the return could just be undefined if the block was dragged into the Stage.

theonlygusti wrote:

Jonathan50 wrote:

Full support.

Ninkancho wrote:

I think the parent would be the stage. But what would the stage's parent be?

The stage shouldn't have a parent. The option shouldn't show in the stage and the return could just be undefined if the block was dragged into the Stage.

The stage shouldn't be another sprite's parent either, unless the ST add local variables to the stage then there is no reason to be able to access its properties.

pvz_pro wrote:

b u m p