[3.x] [Debugger] Add --debug-server CLI option.

[Faless]

Automatically starts the editor debug server at given <IP>:<PORT>.

E.g.:

# Run editor and debug server listening on any interface, port 8080
godot3 -e --path proj/proj_empty --debug-server *:8080

# Run the godot project connecting to that debug server.
godot3 --path proj/proj_empty --remote-debug 127.0.0.1:8080

3.x bits of #52226 .

[akien-mga]

Tested to connect between Linux PC and a Steam Deck, works great!

• Ran Linux PC editor first with: godot-3.x -e --debug-server 127.0.0.1:6007
• Then ran exported debug build on Steam Deck with Jetpaca.x86_64 --remote-debug 192.168.1.7:6007 (that's my Linux PC IP)
• Profit :) Remote scene changes and inspection work fine. Had issues with script reloading but that's not related to this change, I have it also with a localhost connection.

[akien-mga]

Thanks!

[rubenwardy]

Hi! Didn't want to create an issue without confirming whether this is a bug or not. If I use --debug-server, I can successfully connect my game to the editor's debugger once. However, once the session ends, you need to restart the Godot Editor for the debug server to open/work again.

Would making Godot keep the debug server open be a proposal or a bug report?

Edit: reading the code, looks like this would be a proposal. I'll let godotengine/godot-proposals#2608 cover that then

Version: v3.5.stable.flathub [991bb6a]

Here's my commands:

flatpak run org.godotengine.Godot -e --path ~/dev/games/mygame/ --debug-server *:6007

./mygame.x86_64 --remote-debug 127.0.0.1:6007
# or
./mygame.x86_64 --remote-debug 192.168.0.20:6007