Thanks for the answer Casey. I've figured out a system that suits my needs perfectly. I had a lot of dynamic datas so I needed something a lot more complex than CPlayerResources. My solution involved creating what I called "NetDataManager" entities set to always transmit, and then played around with datatable proxies to select the destination players/teams. I'm then creating one NetDataManager entity per world object I want to broadcast, and mirroring some of the properties of the source object that I want to broadcast.
Regards, Spk Nuclear Dawn - www.nuclear-dawn.net
From: Casey Bodley <[EMAIL PROTECTED]> Reply-To: [email protected] To: [email protected] Subject: Re: [hlcoders] Networking Minimap entities Date: Sun, 22 May 2005 15:28:28 -0400 I honestly think that the CPlayerResource class approach is the best. It really doesn't matter how your class sends/stores that data, since it'd just be abstracted by functions like C_PlayerResource::GetFrags( int index ). It's probably not worth the trouble of getting it to network custom data structures, especially because the existing network var types are optimized already. My suggestion would be to break up the problem into two parts, players and structures. For players, extend the CPlayerResource class to send the player's x and y values (it already handles the team). For your structures, I assume you have server-side entities for each? You could network each of these, to send only the position and type. By overloading ShouldTransmit( const CCheckTransmitInfo *pInfo ) in the server class, you can return FL_EDICT_DONTSEND when pInfo->m_pClientEnt isn't on the corresponding team, and FL_EDICT_ALWAYS when they are. This will probably require a function like: int UpdateTransmitState() { return SetTransmitState( FL_EDICT_FULLCHECK ); }. I realize that this doesn't directly answer your initial question, but hope it helps nonetheless, Casey epicar at dystopia-mod.com
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders

