I believe that on the F8 > Tools > Network Event Log. When you receive/emit an event it should show the event payload. This would substantially help with debugging, as we wouldn’t have to print and it would be readily available. Not much more to add, maybe make it so it has a copy function so you can copy the payload.
4 Likes
Good point. However, somewhere along the way I feel this might be something people will have abuse concerns about, so this might be something added with future in-game overlay ‘dev widget’ work as a requirement there is for it to recognize server permission setups as a ‘quick check’.
4 Likes
Could I ask how this could be abused?
I think it would be a very good method of debugging for both players and developers, developers could ask players for their response payload to see what the cause of their issue is etc.
1 Like
You join a server, open the Network Event Log, look at the payload being sent to you, makes it a lot easier for the end user to be able to repeat the data being sent if they were to “hack”, on top of other things.
This might be very good option for debugging networking but in my opinion there must be server convar for enabling this feature to prevent client abusing and minimize risk of hacking and detecting vulnerables by players.
I still don’t get how the event payload will reveal server vulnerabilities. Honestly, if your server has vulnerabilities, then it should be resolved.
By leaking the events payload, cheaters/hackers could re-run event, and money “hacks”, etc arise… which although should be fixed server sided on the servers end, would be hard to get everyone on the same page.
Although having it enabled/disabled through a convar sounds like it could possibly work out.