Run Ons (and Indents, also Selectors, READ OP TO UNDERSTAND, DO NOT ASSUME)

AidyGamer60

run (... :: stack) on {
} :: control

What it would look like in 2.0 ^^

What it would look like in 3.0 ^^
—
So, you see this block? It's a C block, with an indent. What's an indent, you say? Well, an indent is a useful block hole you can use to add a block into something. For example, in Run On, it runs on multiple objects. However, how does this work? Well, here you go:

[sprites v][Sprite1 v] :: custom-arg stack control

This is a Selector. It can be used to select certain objects. It can also be like this:

[sprites v][Sprite1 v] :: custom-arg control

So, if you need to have certain selections inside of any block, you can use that.

So, how Run On can be used, here's an example:

run (say [Hello!] :: stack) on {
[sprites v][Mina v] :: custom-arg stack control
[sprites v][Christopher v] :: custom-arg stack control
[sprites v][Cercia v] :: custom-arg stack control
[sprites v][Manuel v] :: custom-arg stack control
} :: control

This code would run all of the code on sprites. However, some blocks wouldn't work, like

switch costume to [costume5 v]

and

wait () secs

So, I swear if this is a dupe, I'm gonna blow. I spent literally 1 hour on this, and if it's a dupe, all of my work would be wasted for nothing.

Why not control color? It matches this.

Last edited by AidyGamer60 (Feb. 14, 2021 16:44:49)

AidyGamer60

message deleted

Last edited by AidyGamer60 (Feb. 14, 2021 02:14:30)

Steve0Greatness

AidyGamer60 wrote:
So, I swear if this is a dupe, I'm gonna blow. I spent literally 1 hour on this, and if it's a dupe, all of my work would be wasted for nothing.

exact reason why I don't generally make topics on the suggestions forums.

I looked up your suggestion, I couldn't find a dupe

Last edited by Steve0Greatness (Feb. 14, 2021 02:18:52)

pavcato

Duplicate, but I don't know if it's close enough.

Last edited by pavcato (Feb. 14, 2021 02:31:01)

AidyGamer60

This dude literally goes on my topics and tries to find anything even REMOTELY CLOSE to my suggestions, stop.

Last edited by AidyGamer60 (Feb. 14, 2021 02:22:36)

pavcato

AidyGamer60 wrote:
pavcato wrote:
Duplicate, but I don't know if it's close enough.

This dude goes to every topic and tries to find ANYTHING THAT IS EVEN REMOTELY CLOSE TO A SUGGESTION.

Yeah, it's called being a forumer.
Close your tags!
oh my god how many broken tags do you have i had to add 4 end tags

Last edited by pavcato (Feb. 14, 2021 02:25:42)

AidyGamer60

This is basically a completely different suggestion because it has way more content than that and is on a different subject. I'd say this is the inverse of ‘run from sprite’.

Steve0Greatness

pavcato wrote:
Duplicate, but I don't know if it's close enough.

that seems to be suggestion a block that runs the script on 2 sprites, this suggestion seems to be that you can do a single block on 1 script

AidyGamer60

How did you get that custom block setup… t e l l m e -

Also it's slightly incorrect because the Selectors are yellowish-green unlike the others. (I'm not trying to point everything out I'm sorry–)

Last edited by AidyGamer60 (Feb. 14, 2021 02:33:21)

AidyGamer60

ScratchCatHELLO

I think it should be the other way around (with the selection of sprites in the top and the code inside the C block).
Couldn't you just use broadcasts?

the2000

ScratchCatHELLO wrote:
I think it should be the other way around (with the selection of sprites in the top and the code inside the C block).

This. The current implementation seems needlessly complicated. It should be:

run in [Sprite1 v] {
bleh :: grey
} :: control

C blocks were literally created so that block inputs could exist

Steve0Greatness

AidyGamer60 wrote:
How did you get that custom block setup… t e l l m e -

https://Scratchblocks.github.io (am I allowed to share that link?)

Also it's slightly incorrect because the Selectors are yellowish-green unlike the others. (I'm not trying to point everything out I'm sorry–)

Well, that shade is ugly, and bad, and horrific, and ungud. So I made it the color of sensing(as that seems to be the most realistic.).

Last edited by Steve0Greatness (Feb. 14, 2021 03:48:15)

Ihatr

Steve0Greatness wrote:
AidyGamer60 wrote:
How did you get that custom block setup… t e l l m e -
https://Scratchblocks.github.io (am I allowed to share that link?)

Yes, you are allowed. It doesn't link to anything bad and follows all website guidelines.

AidyGamer60

Made it orange!

Last edited by AidyGamer60 (Feb. 14, 2021 04:26:13)

the2000

AidyGamer60 wrote:
Made it orange!

Can you give your opinion on my proposal?

fdreerf

Isn't this just broadcasts with extra steps?

Steve0Greatness

fdreerf wrote:
Isn't this just broadcasts with extra steps?

yeah…

PkmnQ

I think if you need to implement it this way, you should at least make it an entirely different input.

-EmeraldThunder-

the2000 wrote:
ScratchCatHELLO wrote:
I think it should be the other way around (with the selection of sprites in the top and the code inside the C block).
This. The current implementation seems needlessly complicated. It should be:
run in [Sprite1 v] {
bleh :: grey
} :: control
C blocks were literally created so that block inputs could exist

I think it should be a modified version of allowing you to use less blocks.

run in [Sprite1 v] [Sprite2 v] @addInput{
...
}::control

Discuss Scratch