http://blogs.msdn.com/shawnhar/archive/2008/09/24/networkgamer-id-in-xna-game-studio-3-0.aspxAll network games need to send data from one machine to another. To make sense of this data, it is important to know which player it refers to. For peer-to-peer games, this is trivial. When you call LocalNetworkGamer.ReceiveData, you get an output parameterenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/shawnhar/archive/2008/09/24/networkgamer-id-in-xna-game-studio-3-0.aspx#8965001Thu, 25 Sep 2008 16:16:20 GMT91d46819-8472-40ad-a661-2c78acb4018c:8965001BenS1<p>Excellent, that'll help me simplify my network code quite a lot!</p> http://blogs.msdn.com/shawnhar/archive/2008/09/24/networkgamer-id-in-xna-game-studio-3-0.aspx#8965156Thu, 25 Sep 2008 18:34:32 GMT91d46819-8472-40ad-a661-2c78acb4018c:8965156Rim<p>Somehow the image of Paul with a shotgun and the Lady Jessica camping is an afront to my fond geeky recollection of that tale, but in a good way :)</p> <p>Looks like the network library is shaping up very nicely, I'm looking forward to checking it out soon. From the sound of it, it should go a long way in detraumatizing me from my Managed DirectPlay experiences.</p>