-- [ Picked text/plain from multipart/alternative ] You need to send it at least once (for each client) for it to be created/acknowledged clientside. Why would you want to do this?
It shouldn't be using any bandwidth if you're not moving it on the server or changing any of its network vars.. in which case it'll only transmit when stuff is being changed. On 10/29/06, Skillet <[EMAIL PROTECTED]> wrote: > > -- > [ Picked text/plain from multipart/alternative ] > I'm trying to create an entity that has a visual representation on the > client separate from it's server counterpart, with the only networking > occurring when the entity is created on the server side (like a temp ent) > to > keep bandwidth use down. So what I've been trying to do is create the > entity on the server with CreateEntityByName(), then disable its > networking > once the creation and initial network data has been transmitted. Problem > is, simply changing UpdateTransmitState() to return FL_EDICT_DONTSEND > after > the server creation call doesn't work, it causes the entity to never be > created on the client side. Anyone know how to do this? > > I've also tried FL_EDICT_FULLCHECK in UpdateTransmitState() with the logic > moved to ShouldTransmit(), same thing happens. > -- > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlcoders > > -- _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
