When defining custom RPCs in Go using the initializer.RegisterRpc, everything works correctly when called from the client.
However, RPCs that include a slash prefix (/) in their ID (e.g., "friend/suggest") cannot be called from the Nakama Console → API Explorer.
The API Explorer returns a 404 Not Found error, while the same RPC works fine from client calls.
For example, the RPC notification_send (which does not contain a slash in its name) can be called successfully from both the client and the API Explorer, so the issue only affects RPCs that include / in their IDs.
It’s also worth noting that if the same setup is run locally via Docker and accessed from http://localhost:7777, the API Explorer can successfully call the RPCs.
