{.networked.} procedures (not direct sends) send data to the connection that called the RPC

[RattleyCooper]

Check the example here:

https://github.com/RattleyCooper/nettyrpc-1/tree/examples/example/authoritativeChatClient

The client displays it's own chat message as if it came from another person:

# client.nim
proc display_chat(name, message: string) {.networked.} =
  ## Display chat message from the server.
  eraseLine()
  echo fmt"{getClockStr()} {name} says: {message}"

proc send_chat(name, msg: string) =
  # If you want client actions to take place instantly, create a procedure 
  # to handle client-side logic and then dispatch the RPC.
  eraseLine()
  echo fmt"{getClockStr()} You said: {msg}"
  rpc("send_chat", (name: name, msg: msg))

it should call the rpc on other clients, but it is sent to the caller of the rpc as well. If you send a chat you will see both messages in the chat.

[RattleyCooper]

Is this something that we should let the user implement? It's really pretty easy but the user would end up making the same kind of loop to manage it, ie:

# server.nim
proc send_chat(name: string, msg: string) {.networked.} =
  ## Dispatch chat messages to all connected clients regardless of who sent it.
  for c in nettyrpc.reactor.connections:
    if c != conn:
      rpc(c, "display_chat", (name: name, msg: msg, originId: conn.id))

I suppose that in the context of game development, we would want the rpc to go to the connection that called it though. Should we have a way to exclude the origin of an RPC from getting the response for situations where it doesn't need one?

Feel free to close this if you think it's not an issue. The user can definitely implement something like this if they need to but might be worth considering. The more I think about it the more I feel like it's probably a non-issue

[beef331]

We could add a message flag, which can be used to send more information, such as noResponse so the packet would look like
MessageKind, MessageFlag, data. then calling it would look like r rpc({noResponse}, "send_chat", (name: name, msg: msg)) or a short hand of rpcNoResponse("send_Chat", (name: name, msg: msg))