Game Development Stack Exchange is a question and answer site for professional and independent game developers. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I once heard that Runescape "ticks" every 0.3s, and that seemed like a very long period of time, although Runescape is kind of a slow game.

I'm building a more dynamic top-down shooter game, and I'm wandering, how often should I communicate with the server? ASAP, or every 0.1s? How do shooter games usually do it?

Both the server and the client are written in Javascript, node.js and are being used.

share|improve this question
how much responsibility is given to what parties: do clients update to send new data to server, so server can propagate to other clients? does client send a command request to the server, and wait for propagation from server? does the client send a command request, and still attempt to update while awaiting for propagation from server? some of these demand higher frequency of update then others, and effect what happens when connection is lost. – gardian06 Jun 12 '12 at 19:19
up vote 5 down vote accepted

30 times per second is a common packet rate, but that's really a very very small part of te equation.

Check out Networking for Game Programmers for a great intro article to game networking for latency sensitive designs like shooters.

share|improve this answer
Updated with link, let me know if it's wrong. – Byte56 Jun 11 '12 at 20:09
Thanks on the link! – jcora Jun 11 '12 at 20:18

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.