Back to General and Gameplay Programming

running the client/server on the same computer

billybob · 2004-02-07T18:59:07

I''ve read that a lot of high quality game engines have a client, and server system. there is a client running per player, and one server for the game. with single player, there is a client and a server on the same computer. luckily, I decided to go for a heavily OOP style game core, so at this point it wouldn''t be too terribly hard to convert to this client/server system. the problem I have with it is the fact that many things involving game updates would be run twice, once for the client, once for the server. collision detection is the big one I''m worried about. assuming it takes 15 ms to render, and 4 ms to run a game update, that is potentially 4 ms completely wasted, as it will be run twice on the same computer. I guess you could get away with only doing collision for the player for clients, but I imagine there would still be a LOT of things ending up where they shouldn''t between packets my question is how do you make as little single/multi mode specific code as possible, without doing too much twice?