RPC Not Getting to Component Ordered Below the Caller

ASSUME A SCENE LOOKS LIKE THIS:

GameObjectA
–Component script RpcSender
–Component script RpcReceiver

It appears that an RPC called from RpcSender never gets to RpcReceiver.
If I reverse the order of the components on GameObjectA, like below, then the RPC works.

GameObjectA
–Component script RpcReceiver
–Component script RpcSender

I have not tested this thoroughly to know if something else is going on, but is this a known RPC "feature?

Hoping for enlightenment.
Thanks.

– Paul

An RPC gets called on the GameObject where the NetworkView is attached to.
It will hit the first method it comes acros that matches.

I still don’t understand, but I was not as clear on the situation as I should have been.

This fails:

GameObjectA
–NetworkView
–Component script RpcSender
–Component script RpcReceiver

This work:

GameObjectA
–NetworkView
–Component script RpcReceiver
–Component script RpcSender

I don’t know if that helps or hinders.
When you said, “the first method it comes across”, I assume that the manner in which it searches for the “match” is deterministic.
Do you know what the “search” pattern it follows is?

– Paul