Scratch 0.1 had this kind of feature where one sprite could control another sprite. It’s something this person talks about in their thesis https://dn710204.ca.archive.org/0/items/tbca-archive-backup/davefthesis.pdf

What I got out of this was that the Scratch Team rejected doing this because the intertwining of the sprites made it hard for beginners to understand their projects.

This is what it looked like in Scratch 0.1



The “cat” movement logic can’t be seen by just looking at its sprite and the sprite can’t be inserted into another project without the “owner” sprite.

I don’t think this is a TOLORS sort of rejected suggestion but it is something that the team once tried and decided not to do.

10goto10 wrote:

Scratch 0.1 had this kind of feature where one sprite could control another sprite. It’s something this person talks about in their thesis https://dn710204.ca.archive.org/0/items/tbca-archive-backup/davefthesis.pdf

What I got out of this was that the Scratch Team rejected doing this because the intertwining of the sprites made it hard for beginners to understand their projects.

This is what it looked like in Scratch 0.1



The “cat” movement logic can’t be seen by just looking at its sprite and the sprite can’t be inserted into another project without the “owner” sprite.

I don’t think this is a TOLORS sort of rejected suggestion but it is something that the team once tried and decided not to do.

yeah… when I look at it, it is kind of confusing

used to exist, was removed probably to be replaced the broadcasting system

jmdzti_0-0 wrote:

used to exist, was removed probably to be replaced the broadcasting system

yep, used too exist in 0.x, removed later and replaced with broadcasting blocks