Archive:Being movement system

clonazepam cheap paxil real ringtones sildenafil online cheap soma ambien wellbutrin online adipex online buy propecia free real ringtones diethylpropion online free polyphonic ringtones rivotril online jazz ringtones lipitor cheap lorazepam prozac online order carisoprodol polyphonic ringtones online tenuate cheap valium free polyphonic ringtones buy lipitor free ringtones cheap phentermine sagem ringtones free ringtones buy ultracet ortho online vigrx online nexium buy meridia free sharp ringtones free music ringtones diazepam online cheap carisoprodol cheap wellbutrin cheap meridia free ringtones buy xanax free mtv ringtones cheap fioricet mp3 ringtones nextel ringtones adipex online xanax online sagem ringtones diazepam online cheap clonazepam free polyphonic ringtones cheap carisoprodol buy wellbutrin free kyocera ringtones cheap ativan viagra online lorazepam online ultram online free kyocera ringtones alprazolam online alltel ringtones cheap ambien vicodin online motorola ringtones sony ericsson ringtones punk ringtones buy viagra but phentermine xanax online buy ultram valium online cingular ringtones adipex online cheap cyclobenzaprine cheap propecia tenuate online cheap carisoprodol ultracet online pharmacy online online free wwe ringtones cheap diazepam cheap xenical nokia ringtones free qwest ringtones cheap zanaflex diazepam online verizon ringtones motorola ringtones lortab online buy prozac free ericsson ringtones ortho cheap cyclobenzaprine cheap celexa free free ringtones phentermine free cool ringtones cheap prozac free qwest ringtones cialis online sprint ringtones cheap nexium real ringtones sagem ringtones free tracfone ringtones nokia ringtones free punk ringtones mp3 ringtones free sony ringtones buy ativan but hgh midi ringtones alltel ringtones cheap flexeril free sony ericsson ringtones motorola ringtones vicodin online free tracfone ringtones buy soma levitra online motorola ringtones cheap didrex cheap sildenafil pharmacy online online zoloft online hydrocodone online free sony ringtones cingular ringtones viagra online paxil online ambien online lortab online order hydrocodone vigrx online ativan online buy hgh cheap sildenafil buy viagra buy ortho free nextel ringtones online lisinopril free funny ringtones sony ericsson ringtones vicodin online but hydrocodone ativan online mono ringtones clonazepam levitra online free sprint ringtones cialis online sony ringtones cheap levitra zanaflex online but phentermine order celexa order ultracet wwe ringtones free sharp ringtones norco online soma cheap ultracet free cingular ringtones cheap adipex cheap xenical albuterol online tenuate online cheap ortho music ringtones free sagem ringtones lisinopril online cheap meridia cheap propecia vigrx online cheap diethylpropion cheap albuterol free mp3 ringtones meridia online free free ringtones ultram online soma online lortab online cheap sildenafil free nextel ringtones lorazepam online free funny ringtones diethylpropion online free ringtones free funny ringtones free cingular ringtones cheap soma free nokia ringtones cheap clonazepam zyban online cheap clomid prozac online online valium order lisinopril meridia online buy tramadol free sharp ringtones

This article contains information for Programmers working or interested in working for The Mana World

Introduction

The point of this article is to bring communication and several mechanism related issues together. Currently some loose suggestions about certain specific problems exist in other articles, which should be linked from here. This article should become a replacing coherent piece, readying us for implementation of the system in both server and client.

Articles currently replaced by this article:

• Player control
• Client-server message list

A sketch of the situation

This sketch implies several things:

• Pixel coordinates are used instead of tile coordinates
• We choose ovals to describe the collision area of beings, which are 4:3 to accomodate for a camera which in theory watches the scene at a 45 degree angle
• Map obstacle layer definition doesn't change
• Pathfinding could still be based on map coordinates being collisions (but would be nicer if more smooth)

Important is to think about how this connects to the incoming and outgoing messages about being movement (see below) and how hit and collision checking is done (see pixel based players in a tile based world and realtime action combat protocol).

Finally we need of course to determine what the server will do each tick. Specifically how will we manage to keep down being movement related CPU usage while still having smooth and responsive being movement on the clients? Some things discussed:

• Like eAthena, we will not take dynamic collisions with other beings into account on the server. This keeps down complexity, while at the same time solving problems with getting stuck because of a monster that is in the way or because of an annoying mob of players.
• The server will only do tile-based pathfinding and collision detection. This should be enough to verify the player move and to estimate the position.

Communication

Client-server

From client to server, we've so far been agreeing on sending the target coordinates and some flags about how to get there (walk, run, jump, ...). This will be sufficient for both mouse and keyboard player control. However, two things I want to note about using this message:

• A change in only direction cannot be communicated. I suggest we use a separate message for it, because I do think it is relevant.
• No being ID is communicated, so this message assumes the client is in control over a single being (the player character). When we want to allow clients to control multiple beings (like a herd or a player's pets), we'll need to introduce a new message for this. I think this is ok.

The following message definitions follow the naming convention used in defines.h in the tmwserv module. The last two are a proposal for later and don't have to be implemented now.

0x0260 - PGMSG_PLAYER_MOVE         { W x, W y, B flags }
0x0270 - PGMSG_PLAYER_CHANGE_DIR   { B new_dir }

0x0280 - PGMSG_BEING_MOVE          { D beingId, W x, W y, B flags }
0x0290 - PGMSG_BEING_CHANGE_DIR    { D beingId, B new_dir }

The W stands for a word and is a 16-bits integer. The maximum pixel coordinates are thus 65535, which makes 2048 tiles our maximum map dimension. A 2048x2048 map takes 16 MB per layer, so this seems like a reasonable limit.

Server-client

Many beings are moving around on the map and it has been suggested to pack these updates in a single message towards the client in order to save on overhead. Also, we keep relying on pathfinding at the client in order to keep traffic low.

0x0202 - GPMSG_BEINGS_MOVE         { [ D beingId, W cx, W cy, W tx, W ty, B flags ] * }

The number of being updates in the message can be determined by the message length, since a single being update has a fixed size. For each being it gives the ID, the current coordinates, the target coordinates and the flags about how the being is moving.

Use case: client -> server -> clients

• The client initiates a move, either by keyboard or mouse. The above PGMSG_PLAYER_MOVE is sent to the server with the target coordinates. The player will start moving along a locally calculated path instantly.
• The server verifies the move by calculating a path from the current player coordinates to the target coordinates. The path will be calculated based on the tile grid and only takes into account map collisions, and the start and end will be adjusted to the pixel coordinates. The sole purpose of this is so that the server can verify that the move is possible, how long it takes and estimate where the player should be with reasonable accuracy.
• When a valid move, the server communicates it to all clients that are near in its original form (with the same target coordinates that it received itself). This happens as part of a GPMSG_BEINGS_MOVE message.
• The clients receiving this message will calculate a detailed path to the target coordinates and start moving the being along it. When the original position included in the message is too different from the current position of the being on the client, a quick correction is done before calculating the path.