|
This article or section is undergoing major changes by A-MARIO-PLAYER (talk | contribs) and may be incomplete. Please avoid making large edits to this page until this template has been removed. (December 2024) |
|
This article is a stub. It may be incomplete, unfinished, or have missing parts/sections. If the article can be expanded, please do so! There may be suggestions on its talk page. (December 2024) |
Debugging Help is a dialogue in the Scratch Program that gives help on debugging scripts. It was added as part of a major Scratch 3.0 update on the 16th of December, 2024.
The Debugging Help dialogue can be opened by clicking on "Debug" in the Header.
When clicked, the debug button opens a dialogue with 13 different sections including different tips to help the user understand the issue within their project. It goes through different ways the user may have made a mistake in their code, and gives instructions on different methods to try to fix their project, like timing, sound checkpoints, and adding comments to the code.
Getting Unstuck
This is an explanation of each of the tips in the Debugging Help dialogue.
Read Aloud
Read the code aloud. One should notice if they have steps that shouldn't be there, if their code is clear, and if the required instructions are included when starting the project.
Break It Down
Separate the blocks into smaller chunks, and click them to see what they do.
Slow It Down
Add wait () seconds or wait until <> blocks so that one can see what is going on.
Add Sound Checkpoints
Similar to "Slow It Down", add sounds at key points using the play sound ( v) until done block. If a sound doesn't play, the bug may be happening earlier in the code.
Tinker with Block Order
Adjust the order of the blocks, and try using conditional blocks or loops.
To Loop or Not to Loop
If blocks that repeat scripts are used, check that all blocks inside should be looped, and if any blocks inside should only run once.
Think About Timing & Parallelism
Add waits, broadcasts, or user interaction to see if anything changes.
Think About Block Options
Use similar but different blocks, such as swapping out start sound ( v) for play sound ( v) until done.
Check the Values
If variables or other Reporter Blocks are used, check the value at the moment the code sequence is run.
Check Code Sequence
Ensure a script is attached to the correct sprite. If it needs to be moved, drag it to the correct sprite and drop it when the sprite wiggles.
Comment Your Code
Add comments to one's code, and explain what the code does.
Take a Break, Step Away
Take a break away from Scratch, and do something else. After enough time, the Scratcher can return to Scratch and attempt to solve the issue again.
Ask for Help
Ask the Scratch Community to help with debugging the script. Ask for help in a comment or the project's notes. Ask a small amount of people to try the code as they may have different solutions.
