Debugger feature: See the event sheet run in slow motion

[Sig]

Please make sure to follow the forum’s rules before posting.
Posts that do not follow the rules will be ignored, closed and archived.

Would be great to have a feature for the debugger where you can see the event sheet get executed in slow motion next to your game preview. So each event currently being tested and acted on would light up. Condition could light green if positive, red if negative.

Often when I have to debug I end up creating tons of debug variables and test elements to see if things are getting executed in as intended. Would make my workflow much faster if I could directly see the event sheet get executed and see where I have made an error.

[ZeroX4]

I think we should have both

Per frame debugger (step by step debugger?)

Imagine having condition or whatever That if its true it would make your game advance only one frame But otherwise your game would be paused For example When you press some key let’s say Z Your game advance one frame But otherwise its paused at current frame We can totally make some variable change or play sound or tint something if WHATEVER is happening in our events BUT imagine being able to frame by frame observe WHEN exactly or more likely after WHAT something is happening Imagine h…

[AnselGames]

I did see something about Gdevelop Breakpoints being implemented by a community member on GitHub. So if it turns out to be the same as VS Code and other code editors, we could have most of what you requested.

[Bouh]

Indeed, there is an action to stop execution at the point of the action, called a breakpoint.

Making event sheets a big blinking garland is an innovative idea. Normally, to visualize a flow, a programmer puts console logs wherever they are needed, which is also an action already available.

On some projects I work on, I have a debug true/false variable that activates a lot of console logs in my events, and with it, I know what is happening.

There are also gameplay tests, which are made to test games and return what is going wrong by running the game at X1, X4, or as fast as possible.

See the documentation for existing features that I talk about.