The only way I can see that wouldn't work is if the object you dragged onto the localPlayerObject variable was a prefab instead of an instance of a prefab.

This probably is no necessary any more but here is what I found, having the same problem.

Theory: To send a message you receiver should be in the game object as the one you are sending it. It would look useless but the whole idea is to add scripts to an object without bothering about references, so different script doing different things having a function with the same name can be attached and remove to the same object on different times during runtime. Component.SendMessage

The problem: Since you are just sending a message but your receiver is in another game object, its impossible for the message to be receive across game objects.

Solutions:

• having a reference to the object with function you want to send the message to and calling its function directly (as SendMessage would be pointless)
• having a father/root in common, taking its reference and using BroadcastMessage function to call the function, kind of like:

transform.root.BroadcastMessage("myFunction")

of course this could lead to calling all the functions with that name

• sort your game objects by purpose nesting into empty GameObjects, having a manager to reference the head of each group and call BroadcastMessage on each head
• and... well, thats all that came to my mind, I used the first solution since it blend well with my problem.

hope this help anyone,

cheers,

As far as I can see, what you have - as written - should work. This means the problem must be somewhere else, presumably in how you have your objects and scripts set up in the hierarchy.

Make sure:

• You aren't mixing script types (c# and JS)
• You have the script containing the "StartSending" method attached to the "localPlayerObject" (not one of its children)

Hm, I've just seen Eric5h5's answer and he's probably right! :-)