braxbroscratcher wrote:

Good idea, but can't you use the backpack?

braxbroscratcher wrote:

Good idea, but can't you use the backpack?

chexbox wrote:

braxbroscratcher wrote:

Good idea, but can't you use the backpack?

The block libraries would mean that all the scripts could be added at once - without taking up the space.
_____

Would the library be saved with the project? Or would it need to load it every seperatly?

Happysoul05 wrote:

full support. i've been thinking about this but..
You can make extensions be your libraries (that requires javascript knowledge and developer mind).

LuckyLucky7 wrote:

Block Libraries are sections of blocks in one category, similar to how adding extensions works.

Whenever you define a block, sometimes, the block is very useful and commonly used, like this block:

switch costume to [previous costume v]::custom

What if you can make your own block libraries?
Your Block Libraries would be in the “More Blocks” category.
For example:

Gliding Blocks

glide to [Sprite1 v] in a [zigzag v] pattern::custom

glide to edge::custom

The definitions of the blocks would be saved in a Scratch server.
You could also backpack libraries by selecting the library(the whole library would be in a box), then dragging them to your backpack.

PkmnQ wrote:

LuckyLucky7 wrote:

-snip-

I don't see how this is wrong, although I can deal with having to look for a single block in a sea of lots of them, so semi-support!
And by the way, those blocks with dropdowns? Hard to make.

define copy (input) into (output)
if <not<(input)=(output)>> then
delete (all v) of (output)
clear counter
repeat(length of (input) :: list)
incr counter
add (item (noop::) of (input) :: list) to (output)
end
end

copy [list1 v] into [list2 v]

Mr_PenguinAlex wrote:

Support! Although, if this was added, would the library be there in other projects? Like, if you made the library on one project, would the library be on another project as well?