I’m currently working on a system to synchronize Nebula 3 game entities via the network.  I’ve made a component that allows you to register attributes of an entity that you want to be distributed. When the game server creates an entity an ObjectView, which keeps track of the attributes, is automatically created and registered with a DistributedObjectServer.

The DistributedObjectServer regularly goes through all registered ObjectViews and ask if any of their attributes have been changed. Any changed attributes are packed into a message along with the ObjectViews ID and sent to all clients.

The clients are then supposed to relay themessage to their version of the ObjectView which interprets it and updates the attributes, but this hasn’t been properly tested yet.

What I’m going to do next is create a game server/client to test the system.

Be Sociable, Share!
Comment Feed

No Responses (yet)

You must be logged in to post a comment.