• Extensible and integrable scripts, easy installation into your project
  
• Act as normal sprites until loaded as modules into other projects
  
• Prevent variable scope collisions, remove clutter, use premade functions to save implementation time
  
• Easy and intuitive for beginners to understand, a kid-friendly version of package managers
  

• “Create Module” button makes the current sprite a module then prompts the module name. “Delete Module” button makes the sprite a normal sprite.
  
• “Add Module” to import modules from other projects.
  
• List of installed modules with delete buttons, and a URL input for a Scratch project ID and module name. Red light next to the module name means the project was unshared, grace period to find a new module.
  
• Installed modules list with parent project links appear by clicking the Modules extension on the project page
  
• Each project can host up to 3 modules and use 10 modules
  
• When saving to computer, it asks the user if they want to package the modules directly into the sb3 file or as a URL pointer (e.g. scratch.mit.edu/modules/project-id/module-name)
  

load (cloud-list v)  :: extension // Loads the module

when (cloud-list v) loaded :: extension hat // Runs code when module  is loaded

([variable v] of (cloud-list v) :: extension) // Variable of module

([add_entry v] [parameter] of (cloud-list v)  :: extension) // Activates function returning a value

<[add_entry v] [parameter] of (cloud-list v)  :: extension> // Activates function returning a boolean

give control of sprite [this sprite v] to module (platformer-physics v) :: extension // Hands over control of the sprite, such as movement, costume management and code execution to the module

stop control of module (platformer-physics v) over [this sprite v] :: extension // Stops the module from controlling the sprite

set [ v] to [] // Set to sprite only and running as module

change [ v] by (0) // Set to sprite only and running as module

when this module loads :: extension hat

define add_entry::extension hat // define appears as module colour if exposed as a module function when creating the block

define (add_entry (parameter)) :: extension hat

define <add_entry (parameter)> :: extension hat

return [thing] :: extension cap

parent sprite [move v] (10) :: extension // Executes operations in parent sprite when control is given: move, change x, change y, go to, direction, costume, effects, sound, sound effects

<controlling parent sprite? :: extension>

<running as module? :: extension>

BitcoinFarmer wrote:

Can't you just backpack things already? Also how about variables are they shared?
Sorry but this seems weird.
-1

Sigton wrote:

Secondly, I'm also disliking the fact people are jumping to conclusions about suggestions. People are picking out the smallest reason to down a suggestion, or just downing a suggestion simply because they don't understand it. For example, I saw this:

Anonymous wrote:

I have no idea what you're asking for. No support until further notice.

This isn't even asking for an explanation before making a conclusion. It was in fact this quote that finally drove me to making this topic. It added nothing to the discussion, and just downed the suggestion before even having the basic knowledge about it to draw a decent conclusion.

Please read the suggestion, and if you don't understand it, ask for clarification.

BitcoinFarmer wrote:

Can't you just backpack things already? Also how about variables are they shared?
Sorry but this seems weird.
-1

CodeComet6161 wrote:

No support.
1. Scripts that crash Scratch
2.

BitcoinFarmer wrote:

Can't you just backpack things already? Also how about variables are they shared?
Sorry but this seems weird.
-1

3. Too complex, even for an extension.

([tan v] of (9)::operators)

BitcoinFarmer wrote:

I don't agree here. The entire suggestion is kind of hard to read but I am giving my best and I feel like this feature would be chaotic and hard to understand rather than intuitive.
Are they scripts or sprites?
Write like an intro to them, a tutorial on how to use them if they existed maybe. That might help explaining.
Are their functions custom blocks? So is it basically sprites with custom blocks for everyone?
If sprites, will they appear in the sprite list?
Will they be saved into the project you want to add them to?
If we can clarify what you want a bit more, maybe we can discuss this better.

0_009 wrote:

This post was too long, I didn't read

BitcoinFarmer wrote:

How do you want to make it that you can give a module values and let it give values back?
Variables are named differently in every project.

forever
bring :: custom
this :: motion
topic [https://scratch.mit.edu/discuss/topic/868641/] :: events
up :: operators
end

_Paymer wrote:

(#18)
When the arguments are countered, the suggestion is ignored forever

kkidslogin wrote:

I love the idea of a library linker for Scratch. Something I feel that Scratch has been missing is the easy ability to use other people's code; it's nearly impossible to interface other code (unless it is designed to) and is always having variable scope collisions. Something like this would make it much simpler, faster, more streamlined, and would accelerate “imagine, program, share” much more than an AI assistant!

_Paymer wrote:

(#18)
When the arguments are countered, the suggestion is ignored forever

Untrue

Blobfish_Industries wrote:

It feels like you want to take a feature that doesn't belong in Scratch, and add it to Scratch. While it would be cool for advanced users, most Scratchers would either find it all too confusing, or never need it. Backpacking already exists, and works fine for most use cases. I can't think of any instances where this would be better than backpacking. Furthermore, what if the module is modified and no longer works? Well now your project no longer works. Backpacking does not have this problem. If the backpacked code doesn't work for your use case, than modify it. I think that modules are cool, but not something Scratch needs right now.

I_wantasheep wrote:

difference between this and custom blocks?