How stop spamming RPC debug

0 votes

Hi!
I hope you are well!
Then, when I put the keyword puppet or master the output is spamming the following debug "rpc is not allowed on node ... Mode is X, master is Y."
I know these keywords are for calling remotely safely, but it gets really annoying to debug when the output just shows up this, for example, when I'm going to give rpc in a puppet updatePos method that calls all the time.
Hi!
I hope you are well!
Then, when I put the keyword puppet or master the output is spamming the following debug "rpc is not allowed on node ... Mode is X, master is Y."
I know these keywords are for calling remotely safely, but it gets really annoying to debug when the output just shows up this, for example, when I'm going to give rpc in a puppet updatePos method that calls all the time.

Godot version 3.3.3
in Engine by (46 points)

1 Answer

0 votes

Even though it doesn't crash the game, I consider that debug an actual error. You only get those when you try to make calls erroneously. You are losing a lot of performance with these wasted calls, somehow.

You need to debug why you're getting that message to fix it; it's not just there for fun. Somewhere, the wrong peers are calling those functions that you label that way. I usually just use remote anyway and I don't think you're missing out on much functionality if you do that.

by (170 points)
Welcome to Godot Engine Q&A, where you can ask questions and receive answers from other members of the community.

Please make sure to read Frequently asked questions and How to use this Q&A? before posting your first questions.
Social login is currently unavailable. If you've previously logged in with a Facebook or GitHub account, use the I forgot my password link in the login box to set a password for your account. If you still can't access your account, send an email to [email protected] with your username.