How stop spamming RPC debug

Archive
1
:information_source: Attention Topic was automatically imported from the old Question2Answer platform.
:bust_in_silhouette: Asked By Amigoimaginario

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.

2
:bust_in_silhouette: Reply From: w411-3

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.