-
-
Notifications
You must be signed in to change notification settings - Fork 21k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network monitor / debugger #28995
Comments
CC @godotengine/network |
For network stress-testing I can recommend GNS3, there you can create a real network topology and introduce packet drops. It's a lot more extra work but it's a proper way. |
Network profiler was added in #31870 We are in process of moving proposals to Godot proposals repository. If you feel like the new profiler is lacking, open a new proposal there. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
TLDR; Some network debugging would be beneficial to the engine.
I'm going to start off by saying thank you to all the devs that make Godot what it is. It has so many great features and is the best game engine I've used to date!
Networking is a core part of many games and can be really hard to debug while writing code. Multiplayer components can only easily be debugged while running it so a networking section would be really helpful. I found myself using tools like clumsy and Netbalancer, but these don't expose the inner workings of the project. It would help to know (during runtime):
The last one is admittedly for a specific case, but I wasn't able to find a tool that would do networking shaping for just one instance of the game (most of the filtered packets by port).
The text was updated successfully, but these errors were encountered: