You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some errors do not crash Godot - for example signals handlers with improper number of arguments. Those are only displayed in the Debugger -> Errors tab in the Godot editor:
E 0:00:00:0588 battle.gd:17 @ @selected_unit_setter(): Error calling from signal 'unit_selection_changed' to callable: 'HBoxContainer(hit_chance_bar.gd)::_on_attacker_changed': Method expected 2 arguments, but called with 1.
However, they do not show up in the VS Code, the Debug Console, or the Output -> Godot Debugger.
When you only always ever run from VS Code, you end up not seeing errors that silently break the game.
Proposed solution
Show the errors from the Godot Debugger -> Errors tab. I wouldn't mind having them in the Debug Console, mixed with my own logs, but at least very visible.
Another option would be to break on those errors, but I don't think this is possible in Godot itself.
Unless, of course, this should already work and it does not for me for some reason?
The text was updated successfully, but these errors were encountered:
You are absolutely correct, errors are not being routed to the debug console! I can't believe I missed that when I rewrote the debugger (and nobody noticed until now)!
Godot version
4.3.stable
VS Code version
1.95.2
Godot Tools VS Code extension version
2.3.0
System information
Windows 11
Problem statement
Some errors do not crash Godot - for example signals handlers with improper number of arguments. Those are only displayed in the Debugger -> Errors tab in the Godot editor:
However, they do not show up in the VS Code, the Debug Console, or the Output -> Godot Debugger.
When you only always ever run from VS Code, you end up not seeing errors that silently break the game.
Proposed solution
Show the errors from the Godot Debugger -> Errors tab. I wouldn't mind having them in the Debug Console, mixed with my own logs, but at least very visible.
Another option would be to break on those errors, but I don't think this is possible in Godot itself.
Unless, of course, this should already work and it does not for me for some reason?
The text was updated successfully, but these errors were encountered: