Home/ Questions/Q 262865
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T22:33:12+00:00

I’ve been writing a 2D flash multiplayer game and a socket server. My original

  • 0

I’ve been writing a 2D flash multiplayer game and a socket server. My original plan for the movement algorithm between the client and server was the following:

  • The client informs the server about the player’s movement mode (moving forward or not moving) and the player’s turning mode (not turning, turning left or turning right) whenever these change.
    • The server loops all players every few milliseconds and calculates the angle turned and distance moved, based on the difference in time. The same calculation is done by the client.

My current calculation for the client (same math is used in server) ==>

Turning

var newTimeStamp:uint = UtilLib.getTimeStamp(); //set current timeStamp
                var rot:uint = Math.round((newTimeStamp - turningTimeStamp) / 1000 * 90); //speed = x degrees turning every 1 second
                turningTimeStamp = newTimeStamp; //update timeStamp
                if (turningMode == 1) //left
                {
                    movementAngle = fixAngle(movementAngle - rot);
                }
                else if (turningMode == 2) //right
                {
                    movementAngle = fixAngle(movementAngle + rot);
                }

private function fixAngle(angle:int):uint //fixes an angle in degrees (365 -> 5, -5 -> 355, etc.)
        {
            if (angle > 360)
            {
                angle -= (Math.round(angle / 360) * 360);
            }
            else if (angle < 0)
            {
                angle += (Math.round(Math.abs(angle) / 360) + 1) * 360;
            }
            return angle;
        }

Movement

var newTimeStamp:uint = UtilLib.getTimeStamp(); //set current timeStamp
                var distance:uint = Math.round((newTimeStamp - movementTimeStamp) / 1000 * 300); //speed = x pixels forward every 1 second
                movementTimeStamp = newTimeStamp; //update old timeStamp
                var diagonalChange:Array = getDiagonalChange(movementAngle, distance); //with the current angle, howmuch is dX and dY?
                x += diagonalChange[0];
                y += diagonalChange[1];

private function getDiagonalChange(angle:uint, distance:uint):Array
        {
            var rAngle:Number = angle * Math.PI/180;
            return [Math.round(Math.sin(rAngle) * distance), Math.round((Math.cos(rAngle) * distance) * -1)];
        }

This seems to work great. In order to take lag into account, the server corrects the client’s info every now and then by sending this data.

With this system very little bandwidth is used to handle movement. However, the differences between my server and the client’s coordinates and angles are too big. Should I maybe extend my “algorithm”, to also take into account the latency a user has? Or are there better ways of handling movement in client<>server multiplayer games with great performance?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    My initial design would be similar to yours, but if that’s not working, perhaps you could allow the client to do ALL the movement and just have the server do some range checking.

    So if your last reported position was X, the next one must be within a radius from X where the radius is based on the difference in timestamps sent from the client with the x,y data.

    Mostly this is just needed to detect cheating.

    Stopping, fighting, etc would require a position be sent along with the attack, and actions triggered by positions would only be triggered after the client sent the update for that position but would be server-based.

    Not sure this would help too much, but it might stop the jolting resyncs you would see from your initial algorithm.

    Comment response:

    No, the clients would still inform the server of their position, but the server wouldn’t try to calculate the next position. This would mean that the server (and all other clients) would be at least one send/receive cycle behind in position.

    I guess I’m saying just let the client do all the work, figure out where the character is and tell the server, but include enough info that the server can optionally check validity to ensure nobody’s cheating.

    The cheat detection could even be turned off for performance or set to randomly check.

    Note: All collision/position info on objects within traveling range would need to be sent to the client for this to work.

    • 0