Snap! Tips - a list of useful tips in Snap!

Tutorials (Here's how to...)
1

Useful Tips in Snap!

This is a list of the most useful tips in the Snap! editor in case you don't know. This is a wiki post, you can edit this post, but:

Rules for editing
  1. Add a tip or some useful information that can help.
  2. Do not be rude.
  3. It must be a tip, don't add some trash stuff.
  4. You should not edit the text above "Tips".

Follow the above rules. Editing this post without following the rules may have a risk of being reverted.

Tips

(you may edit this part and below)

1 - Previous costume

Do not use switch to costume ((costume #) - (1)) block and instead use switch to costume (() - (1)) to avoid the costume from suddenly switching to a turtle.

2 - Debug your code

The button below can be used to slow down scripts to debug your code. This is very useful to check errors. This is known as visible stepping. To enter this mode, click step feet and the button will turn blue and add a slider: image. This slider can be used to control the speed of your program. As you run your program, you can see it progress based upon which block or input is highlighted:

image
image1169×181 58.9 KB

This can be useful for determining where in your code an error occurred. Note that visible stepping does not work within warp blocks. Other helpful parts of visible stepping include:

Single Stepping: When you slide the speed slider all the way down to the bottom, you enter single stepping mode. The pause button is replaced with the single step image button. This allows you to move forward through your code one step at a time.

Debug Variable Scope: When visible stepping is on, one can visually see a variable's scope and where it is defined based upon blue highlighting:
Debugging Scope in Snap!
Reporting as you go: Reporters will show speech balloons to help you know what they are reporting and understand strange behaviours.
Screen Recording 2025-01-23 093245.mp4 [video-to-gif output image]

3 - Random decimal between integers

(pick random (1) to (10))

If both inputs are integers without decimal points, the return value is an integer.

(pick random (1.) to (10))

If you want a random decimal between two integers, put a decimal point after either (or both) integers.

(pick random (1.2) to (3.4)

You can also get a random decimal between two decimals.

Want to add more tips? You can edit this wiki post! Follow the rules!

2

going to dev mode is faster than pressing a setting, scrolling all the way down, and looking through that abnormally large extension menu, and then typing hex sha512 hash rather than selecting it from a dropdown. I would suggest removing that...

3

done. Now what do you want to add? (this is a wiki post, so anyone can edit my post)

4

Huh? I don't understand the alleged problem or solution.

I think this might be a bit of an overreach. :~) My all-time favorite tip would be shift-clicking an arrowhead to add/delete three slots at a time in a variadic input. (I know, it's a wiki, I could add that, but I'm trying to make a more general point here. There are probably a thousand examples I could have used instead, and if people do add them all to a list that's in no particular order, nobody would be able to find the one they need.)

5

It's because switch to costume -1 will go back and loop around to the end, but it will skip the turtle costume (0). If you do the current costume number - 1, it will go to the turtle costume.

6

I'm not sure if this changed in the latest update, but from my experience, this simply is not true for the blocks pick random, for, and numbers from

7

untitled script pic

8

Oh, did the other two blocks change too?

9

No clue, didnt test it

10

Since real numbers are dense, what I think you think this should do for non-integers would result in an infinite (uncountable, in principle) list!

11

It was added in a very recent update, which is most likely why they put it here.