Full support! This would not only help the creator of the project navigate their scripts, but also save data and time when loading the project.

bump

I definitely support as i some times have to experiment with some sort of code, and after i finally figure it out, i have reporters, booleans, if statements, and others every where. i currently have to clean up the blocks, then scroll down looking for all disconnected blocks. this would be very helpful for me.

Support

Support. A certain scratch extension that we are not supposed to name has this, and it is amazing!

I support this idea. I don't like orphan blocks. There are nearly never orphan blocks in my projects.

BasisEssence779 wrote:

I support this idea. I don't like orphan blocks. There are nearly never orphan blocks in my projects.

Lol, same. But think of this as a favor to those who have projects with messy code.

This seems like a very sensible idea. I for one don't like blocks floating around so it'd be nice if unconnected hat blocks and unconnected stack/reporter/boolean/cap/c blocks got removed. I was about to support removal of duplicate scripts but BFDISuperFan's post

BFDISuperFan wrote:

when green flag clicked
hide

when green flag clicked
hide

^ The hide script doesn't do anything different when there is a duplicate.

when green flag clicked
change volume by (10)

when green flag clicked
change volume by (10)

^ In this case, having the same script twice doubles the volume change to 20, instead of 10.

convinced me otherwise.

Support, but with changes. In my opinion there should be just one “Extra clean up” button. Clicking on it would bring up a menu with multiple checkboxes, confirm and cancel buttons. First 2 checkboxes should be what OP stated: Delete all orphan blocks and Delete duplicate scripts

But I also suggest having some extra checkboxes:

Delete unused variables and lists - self explainatory. Already implemented in griffpatch's browser extension.

Delete unused custom blocks - if there is a definition of a custom block with some blocks attached to it, but that custom block is never used it would get deleted.

Clear covered up values - you know how when blocks have some values typed in them(for example by default), but then you put some block on top of it which covers that value. Takeing that block out would reveal that original value is still there. Most of those values will never be used and are pointlessly taking up space in project.json file, which has 5MB limit. I've already made a separate program specifically for it, which also shows amount of bytes by which file size gets reduced and it can be quite significant amount.

Support! In a lot of big games, I see scattered custom blocks, booleans, reporters, etc. everywhere! A way to delete all of those would be awesome!

hurricane459 wrote:

Support

Okay, But please be constructive and explain why you support. I learned this from some other scratcher.

bigbigbigeeveefan wrote:

hurricane459 wrote:

Support

Okay, But please be constructive and explain why you support. I learned this from some other scratcher.

One thing that you should learn is that what you are doing is just as nonconstructive as the post that just says “Support”. To be constructive, you have to contribute something to the discussion, like this:

Vadik1 wrote:

In my opinion there should be just one “Extra clean up” button. Clicking on it would bring up a menu with multiple checkboxes, confirm and cancel buttons. First 2 checkboxes should be what OP stated: Delete all orphan blocks and Delete duplicate scripts

But I also suggest having some extra checkboxes:

Delete unused variables and lists - self explainatory. Already implemented in griffpatch's browser extension.

Delete unused custom blocks - if there is a definition of a custom block with some blocks attached to it, but that custom block is never used it would get deleted.

Clear covered up values - you know how when blocks have some values typed in them(for example by default), but then you put some block on top of it which covers that value. Takeing that block out would reveal that original value is still there. Most of those values will never be used and are pointlessly taking up space in project.json file, which has 5MB limit. I've already made a separate program specifically for it, which also shows amount of bytes by which file size gets reduced and it can be quite significant amount.

Yes, just one extra clean up would be good, but having to click the checkboxes every time would waste too much time. Maybe you could change it in the edit menu?

PkmnQ wrote:

In my opinion there should be just one “Extra clean up” button. Clicking on it would bring up a menu with multiple checkboxes, confirm and cancel buttons. First 2 checkboxes should be what OP stated: Delete all orphan blocks and Delete duplicate scripts

But I also suggest having some extra checkboxes:

Delete unused variables and lists - self explainatory. Already implemented in griffpatch's browser extension.

Delete unused custom blocks - if there is a definition of a custom block with some blocks attached to it, but that custom block is never used it would get deleted.

Clear covered up values - you know how when blocks have some values typed in them(for example by default), but then you put some block on top of it which covers that value. Takeing that block out would reveal that original value is still there. Most of those values will never be used and are pointlessly taking up space in project.json file, which has 5MB limit. I've already made a separate program specifically for it, which also shows amount of bytes by which file size gets reduced and it can be quite significant amount.

Yes, just one extra clean up would be good, but having to click the checkboxes every time would waste too much time. Maybe you could change it in the edit menu?


I didn't realize that griffpatch had an extension for Scratch that pretty much partially addresses my suggestion. If griffpatch thinks about this suggestion, could it be possible that he would end up implementing it?