the blah blah was like this:

because “new scratcher” does not understand, also the “Ask for Help” was supposed to be “ask on discuss forum” because it doesn't allowed for “new scratcher” to use discuss forum so i draw a concept here:

in this feature you can:
-change the existing block by editing on it
-check if the block was something wrong on it?
-show fps and clone counter to check if the project was to laggy

well idk about that but trust me this is going to easy debugging the project

also can i add “coding assistant” like chatgpt? lol

I think the current Debug menu is useful because it encourages Scratchers to think about how they can debug their own program, rather than relying on some external tool to give the solution to them.

But also, I'm not entirely sure how such a Debug menu would work anyway. Scratch has no syntax errors, so the Debug menu would only be useful in deducing unintentional outcomes of the code. But how is a computer supposed to know what you meant to program? If you encounter a bug in Scratch code, it's because the project is doing what you told it to do, in some sense, so how is a debug menu supposed to know what you want it to do?

TheBFDIObjectShowFan wrote:

-change the existing block by editing on it

That sounds too similar to this:

The Official List of Rejected Suggestions

2.2 Text-based syntax in Scratch
Some users wish to code Scratch not with the blocks, but with typing code instead (similar to how more advanced programming languages work). Others are interested in an option to view, convert, or download Scratch code to other programming languages. However, the Scratch Team has discussed this possibility multiple times and has decided every time that it would not be beneficial for beginners or teachers.

This suggestion extends to coding, viewing, converting, or downloading Scratch in any text-based language, including BBCode, Javascript, some form of pseudocode, or some other programming language. If you wish to code using another language, then you can learn it on your own, but it would have to be done outside of Scratch. For those who are interested, it may be worth checking out Tosh. It is a text-based programming language that serves as a text editor for Scratch projects. Another option is MakeCode Arcade, a programming language that can convert between block-based and text-based programming within the editor.

-check if the block was something wrong on it?

How would this be possible? Computers can't read your mind.

TheBFDIObjectShowFan wrote:

-show fps and clone counter to check if the project was to laggy

I agree with this one, this would be useful.

TheBFDIObjectShowFan wrote:

also can i add “coding assistant” like chatgpt? lol

That has already been suggested, please continue the discussion there.

Za-Chary wrote:

I think the current Debug menu is useful because it encourages Scratchers to think about how they can debug their own program, rather than relying on some external tool to give the solution to them.

But also, I'm not entirely sure how such a Debug menu would work anyway. Scratch has no syntax errors, so the Debug menu would only be useful in deducing unintentional outcomes of the code. But how is a computer supposed to know what you meant to program? If you encounter a bug in Scratch code, it's because the project is doing what you told it to do, in some sense, so how is a debug menu supposed to know what you want it to do?

well its to easy..
the debug code will read all code that are still run in project like..



im sorry using “comic” because to hard to explain so hope you understand this..

TheBFDIObjectShowFan wrote:

well its to easy..
the debug code will read all code that are still run in project like..

This is the greatest comic of All Time.

This just seems like text-based coding, then, is that right? What does this have to do with debugging?

Za-Chary wrote:

TheBFDIObjectShowFan wrote:

well its to easy..
the debug code will read all code that are still run in project like..

This is the greatest comic of All Time.

This just seems like text-based coding, then, is that right? What does this have to do with debugging?

like check if something wrong but also theres a feature like.. you can edit like this:

from this:
<when flag clicked>
<move (10) steps>

to this:
<when flag clicked>
<say (hello world) for (2) second>
<move (5) steps>

because you can edit block so easy than going through the sprite or.. you can code without dragging block at all

Maybe they could add a tool to help find scripts (currently Ctrl+F highlights text it found, but it doesn't scroll to the blocks)
That's not text-based coding

nembence wrote:

Maybe they could add a tool to help find scripts (currently Ctrl+F highlights text it found, but it doesn't scroll to the blocks)
That's not text-based coding

but im so confused about that one but this feature still understand enough…

TheBFDIObjectShowFan wrote:

nembence wrote:

Maybe they could add a tool to help find scripts (currently Ctrl+F highlights text it found, but it doesn't scroll to the blocks)
That's not text-based coding

but im so confused about that one but this feature still understand enough…

also i need the some debug script that can easily edit without searching some blocks

Elijah999999 wrote:

TheBFDIObjectShowFan wrote:

-change the existing block by editing on it

That sounds too similar to this:

The Official List of Rejected Suggestions

2.2 Text-based syntax in Scratch
Some users wish to code Scratch not with the blocks, but with typing code instead (similar to how more advanced programming languages work). Others are interested in an option to view, convert, or download Scratch code to other programming languages. However, the Scratch Team has discussed this possibility multiple times and has decided every time that it would not be beneficial for beginners or teachers.

This suggestion extends to coding, viewing, converting, or downloading Scratch in any text-based language, including BBCode, Javascript, some form of pseudocode, or some other programming language. If you wish to code using another language, then you can learn it on your own, but it would have to be done outside of Scratch. For those who are interested, it may be worth checking out Tosh. It is a text-based programming language that serves as a text editor for Scratch projects. Another option is MakeCode Arcade, a programming language that can convert between block-based and text-based programming within the editor.

-check if the block was something wrong on it?

How would this be possible? Computers can't read your mind.

TheBFDIObjectShowFan wrote:

-show fps and clone counter to check if the project was to laggy

I agree with this one, this would be useful.

TheBFDIObjectShowFan wrote:

also can i add “coding assistant” like chatgpt? lol

That has already been suggested, please continue the discussion there.

ok this might be rejected expect a “fps shower” and “clone counter”

but fr.. how people will understand it without some debugging code feature?

It should be called “help” or “get help” and not “debug” because it may confuse scratchers when they move on to programming languages with real debug features into thinking they’re useless

ok this might be support to add “fps checker” and “clone counter”

Za-Chary wrote:

I think the current Debug menu is useful because it encourages Scratchers to think about how they can debug their own program, rather than relying on some external tool to give the solution to them.

But also, I'm not entirely sure how such a Debug menu would work anyway. Scratch has no syntax errors, so the Debug menu would only be useful in deducing unintentional outcomes of the code. But how is a computer supposed to know what you meant to program? If you encounter a bug in Scratch code, it's because the project is doing what you told it to do, in some sense, so how is a debug menu supposed to know what you want it to do?

I agree. When you code something wrong, it's doing what you told it to do, not what you wanted it to do. Computers can't read your mind.

I was thinking of debug blocks like this

log [variable here] :: sensing

it would write the variable and value in a debug log, like in the top post.

pause code :: sensing

this would pause everything and log all the variables in the debug log.

I would also add a pause/play button on the top of the debug log.

TheAutocorrectingCat wrote:

Za-Chary wrote:

I think the current Debug menu is useful because it encourages Scratchers to think about how they can debug their own program, rather than relying on some external tool to give the solution to them.

But also, I'm not entirely sure how such a Debug menu would work anyway. Scratch has no syntax errors, so the Debug menu would only be useful in deducing unintentional outcomes of the code. But how is a computer supposed to know what you meant to program? If you encounter a bug in Scratch code, it's because the project is doing what you told it to do, in some sense, so how is a debug menu supposed to know what you want it to do?

I agree. When you code something wrong, it's doing what you told it to do, not what you wanted it to do. Computers can't read your mind.

It could be like this:

when gf clicked
if <[1] = [1]> then
say [program works fine] for (2) seconds
else
debug error [insert here]::extension
end

Though you still have to manually do stuff like this

how about make the true debug thing
a separate tab along side the current debug menu
problem solved