The Start Block is no longer a part of this suggestion.
The workaround is too simple

Blocks:

stop [script: Placeholder Name v] :: control stack

Block Uses:

Any hat block part of a project will have the ability to have the script named when right clicked.


Mockup

The stop script could be put in other scripts instead of a stop this script inside of 15 if then blocks. I

The reason there is a script: … is because the stop block already has options. If someone named a script “this script” and there was no script: before it, there would be two this scripts and a user would have to guess which one is named

Pros: it would be way simpler to stop scripts

Cons: It would be out of the way. (Many users probably wouldn't know of its existence)

I agree. I think that this would make it easier to control and keep track of scripts. I also fixed the block.

stop script [Placeholder Name v]

I put script: <Placeholder name> so if someone named a script “all” it would show up as script: all and not confuse users

Can't you just do this:

when green flag clicked
say []
stop [this script v]

when green flag clicked
think [] for (2) secs
stop [this script v]

linearlemur wrote:

Can't you just do this:

when green flag clicked
say []
stop [this script v]

when green flag clicked
think [] for (2) secs
stop [this script v]

That isn't a workaround.

Really, why cant we just use the

stop [this script v]

block?

EatNYeet wrote:

linearlemur wrote:

Can't you just do this:

when green flag clicked
say []
stop [this script v]

when green flag clicked
think [] for (2) secs
stop [this script v]

That isn't a workaround.

Yes it is, just use stop this script for every script that you want to stop. That would be easier than going through the trouble of naming every script you want to stop.

linearlemur wrote:

EatNYeet wrote:

linearlemur wrote:

Can't you just do this:

when green flag clicked
say []
stop [this script v]

when green flag clicked
think [] for (2) secs
stop [this script v]

That isn't a workaround.

Yes it is, just use stop this script for every script that you want to stop. That would be easier than going through the trouble of naming every script you want to stop.

The problem with doing this is if the stopping is conditional, then you have to copy and paste the code in every script you want to do this to, therefore leaving less room for the rest of the code.

linearlemur wrote:

EatNYeet wrote:

That isn't a workaround.

Yes it is, just use stop this script for every script that you want to stop. That would be easier than going through the trouble of naming every script you want to stop.

<Deleted>

think [] for (2) secs

Would stop on its own. Like EatNYeet said, those aren't workarounds

I already suggested this:

stop [script: Placeholder Name v] :: control stack

what if I add a start block to the suggestion?

start [script: Placeholder Name v] :: control stack

It would restart scripts that had already been turned off.

Pros of the start block:
- It would reduce project size because instead of a duplicate code line for a “when I receive” it would just be a single “start”
- It would give the option to reset code without 15 if then blocks

Cons:
- It could be confusing
- What would happen if the script is already running?

The_5th_Scratcher wrote:

say []

would go on forever. It would never stop. My suggestion can stop that.

The say blocks doesn't work like that. It just sets the contents of the speech bubble and continues running the code after it.

Maximouse wrote:

The say blocks doesn't work like that. It just sets the contents of the speech bubble and continues running the code after it.

Oh

bump (Edited original post)

bump

I support, as this helps to organize scripts and only stop certain scripts.

Nice idea, but I rarely find myself ever needing to stop scripts externally, and this would create confusion for scratchers who don't know about this feature and see inside a project with this.

Also, you would have to comment each script with it's name, unless there was another way to display it's name.

Since you say “organization” I assume we're talking about very large projects. The dropdown menu for the stop block would become unbearably long and unnecessary this way.

Because of the reasons above, no support.

The_Imaginarium wrote:

The dropdown menu for the stop block would become unbearably long and unnecessary this way.

Same with the broadcast dropdown.

Bump

bump