My Blocks

define custom block

The current Define block

My Blocks (known as More Blocks in Scratch 2.0) is one of the ten categories of Scratch blocks. It holds procedures for the selected sprite. They are color-coded pink. Before any blocks are created, it is empty, except for a "Make a Block" button.

Clicking Make a Block brings up a dialogue allowing the user to make a procedure. Once OK is pressed, the new block appears in the palette and an empty definition appears in the code area. When the procedure runs, Scratch will run the blocks below the corresponding Define block.

Activation

The code under this block will be run whenever its corresponding block is run in a Script, similarly to Broadcasts. Unlike Broadcasts, however, the code is run as if it was inserted where it was run from. If the block has been set to run without screen refresh, it will take only one frame to run.

Note:

A block can also run itself from within itself, which is called Recursion, and can be used to solve many complex problems.

Uses of My Blocks

Apart from variables, procedures are the main kind of abstraction used in procedural programming; they let Scratchers write scripts without knowing or thinking about the details of what each script does. This is also true of Scratch's built-in blocks, like move () steps. For example, suppose one wants a sprite to vanish and reappear. To vanish, the sprite should play a sound and repeatedly increase the ghost effect; to reappear, it should repeatedly decrease the ghost effect. This should happen at several points in the project. Without procedures, the Scratcher would have to duplicate the same sequence of blocks at each point, but by making "vanish" and "appear" blocks, they can write scripts in a way which matches how they think of them:

. . .
think [Hmm...] for (2) seconds
vanish
. . .
appear
play sound (Horse v) until done
. . .

define vanish
start sound (Ripples v)
repeat (10)
    change [ghost v] effect by (10)
end

define appear
repeat (10)
    change [ghost v] effect by (-10)
end

This is especially useful in pen projects, where the same shape has to be redrawn multiple times:

when gf clicked
pen up
go to x:(0) y:(0)
draw

define draw
erase all
pen down
forever
  turn cw (1) degrees
  move (1) steps
end

The Make a Block dialog

Now, if the user changes their mind about how the sprite should vanish or appear, they need only change the block definitions.

Custom blocks also help by reducing project file size and allowing the user to disable screen refresh. Number, String, and Boolean inputs can be added to custom blocks. For example, a Scratcher could make a jump ():: custom block with a "height" input, and (height:: custom) will appear in the Define block. These blocks can be dragged out and used in the definition just like variables.

If a user has a long string of code they know they will be using a lot, it makes sense to use a custom block. That way, the user doesn't have to repeat making that code multiple times, and this reduces lag as there are now less blocks.

Use in Calculations

Custom Blocks are also useful when a project relies on specific calculations multiple times. Instead of performing the same operation multiple times, a custom block with number or boolean inputs can be used in conjunction with a variable which returns the result of the calculation:

define Distance away from line (x)
set [result v] to ([abs v] of ((mouse x)-(x)))

when gf clicked
broadcast (start v)
forever
  Distance away from line (x)
  if <[5] > (result)> then
    broadcast (restart v)
  end
end

Note that the result can also be a boolean value:

define Is a positive integer? (number)
set [result v] to <(number) = ([abs v] of (round(number)))>

when gf clicked
ask [Enter the number of cats to display] and wait
Is a positive integer? (answer)
repeat until <(result) = [true]>
  say [The number must be a positive integer!] for (4) seconds
  ask [Enter the number of cats to display] and wait
  Is a positive integer? (answer)
end
broadcast (Start v)

Run without screen refresh

Using custom blocks is the only way to run scripts without screen refresh. Screen refresh is the very minuscule wait which occurs at the end of each iteration of a loop block or when a block which waits is used. The Make a Block dialog offers to disable screen refresh (by default it is enabled.) This can make it less obvious what is happening but is useful if one wants to make changes without the user seeing the intermediate steps or waiting a long time. For example, if one uses this script:

set [i v] to [0]
pen down
repeat (200)
    move (i) steps
    turn cw (92) degrees
    change [i v] by (1)
end
pen up

the user may watch the sprite drawing the picture. But if one places it in a custom block with screen refresh disabled, the user will only see the complete picture, and it will finish much sooner. This feature is commonly used in platformers and other games requiring faster computer processing. It is also used to fix timing issues that are caused by built in pauses in the script, which intends to make on screen motion more visible, but it can sometimes get in the way.

This is not the same as turning on Turbo Mode. Turbo Mode makes projects run faster by decreasing the wait time at the end of each iteration, but the project still runs with screen refresh.

Warning:

Run without screen refresh should not be used with custom blocks that contain any "wait" blocks or loops that will never end as this can freeze and possibly crash the editor.

Note:

Placing other custom blocks set to run without screen refresh inside of a block set to run without screen refresh may contribute to lag.[citation needed]

History

This article or section documents something not included in the current version of Scratch (3.0). It is only useful from a historical perspective.

define custom block

The Define block in Scratch 2.0

Scratch 2.0

The New Block menu in Scratch 2.0

In Scratch 2.0, My Blocks were called "More Blocks". They were purple-colored. The interface where one created a new block was different. For example, there were "number inputs" and "string inputs" which were merged in Scratch 3.0. The 'Define' blocks for them could be found by right clicking a custom block and clicking "define".

Before Scratch 1.0

Main article: Scripts (category)

The top block would run those under the bottom block.

Scratch 13Oct04 script with attributes.

In Scratch 14Feb04 and Scratch 13Oct04, scripts was a block category. The scripts category contained blocks that caused a sprite to take actions as prescribed by the blocks under the corresponding hat block. The scripts category would always be the rightmost in the order listed above the Block Palette.

On creating a new project, the scripts category would initially contain no blocks.

A new block could be added to the scripts category by clicking an arrow in the upper-right corner of the code area, then selecting "new script hat" from the options in the resulting context menu. This would add a block named "script1" (or "script" joined with a different number if there was already a "script1" block) to the scripts category, and a matching hat block to the code area.

Alpha versions of the Define block

A new block would also be added to the scripts category when the user selected "new event hat" from the previously mentioned context menu. The event hat block added to the code area would have a stack block in the scripts category, named for the color of the flag to be detected. A scripts stack block linked to an event hat would tell the sprite that used it to act as it would had the block's flag been waved, in effect waving the block's flag only to the sprite that used the block.

The blocks in the scripts category were specific to the sprite currently selected for the Blocks Palette. In other words, the addition of a block to the scripts category for one sprite would not cause the block to appear for any other sprite.

Once a script would be created, one may right-click the hat block of a script to bring up a context menu, from which additional options can be selected, such as creation of parameters and renaming of the script. The caller block may also be right-clicked, once again bringing up a context menu; this time including options to change the block to one that starts or stops that script, and change it to a "[scriptname] is running" block: a boolean reporter that returns true if the script of the script block it originated from is currently running, and false if not.

The Scripts category was removed in Scratch 28Feb05. Procedures would not be added back until Scratch 2.0.

Glitches

Main article: Scratch Bugs

Typing "%" inside a label text means "Okay" cannot be pressed.

After exiting, the blocks will be bunched up together.

Bunching Blocks Bug

If a custom block with a label saying either %b or %n is placed, then set to a boolean or number/text, it displaces the block and changes it to boolean for %b or number/text for %n.

If a custom block has a label of "%", Okay cannot be pressed (left). The only option is to Cancel and exit. If the block palette is scrolled up after that, the blocks will be bunched up together (right). This can be fixed by unloading the block palette by leaving the sprite, going to the costumes, sounds or seeing project page.

Undefined Hat Block bug

Main article: Undefined Hat Block

The Undefined Hat Block

The Undefined Hat Block is a block that has been generated by an error. It is the only red Scratch block in Scratch 3.0. It cannot be connected with any other block, as it is classified as a Hat and Cap block. One of the ways it can be generated is by naming a Custom Block a backspace character. Attempting to Comment on this block will cause this block to follow the mouse, but going to a different sprite will fix this issue.

Separating Label Text Bug

In the dialog, if you type something (like "hello world") then "%n", and add a Boolean input, then the "hello world" will become "hello worl" and another label "d%n". This bug occurs because "%" is a special character in project saves.

Crashing the coding window

In the dialog, if something (like "hello world") is typed then "%n", and a Boolean input is added, the custom block input panel will only say Boolean. Then, if a label is added, and the OK button is clicked, the code panel will crash, and it will return an error message.

Dynamic scoping

This article or section documents something not included in the current version of Scratch (3.0). It is only useful from a historical perspective.

In early Scratch 3.0, the parameters of custom blocks used to exhibit dynamic scoping, meaning a custom block called by another could access all the first one's parameters. For example, in this situation,

when gf clicked
block 1 (3)

define block 1 (x)
block 2 (4)

define block 2 (y)
say ((x:: custom) + (y)) for (2) seconds

the sprite would say "7". This was fixed shortly after Scratch 3.0's release.

Workaround

Main article: List of Block Workarounds

In most simple cases, custom blocks can be worked around by using broadcasts and variables. However, this would disable screen refresh, or for multiple scripts to use the same procedure at the same time.

when gf clicked
broadcast (jump v) and wait

when I receive [jump v]
repeat (5)
    change y by (6)
end
repeat (5)
    change y by (-6)
end

Common Suggestions

Please expand this article or section. You can help by adding more information if you are an editor. More information might be found in a section of the talk page. (April 2019)

Many Scratchers would like the ability to make custom reporters and boolean blocks. Additionally, dropdown inputs as arguments have also been requested, to the extent that some people used JSON hacking to insert them into custom blocks.