From 43e8fe27b1f8a3f621b222ad5f1152fc9662254d Mon Sep 17 00:00:00 2001 From: Canownueasy Date: Wed, 13 Jul 2011 14:03:17 +0000 Subject: [PATCH] Update MediaWiki page '317 Protocol' --- 317-Protocol.mediawiki | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/317-Protocol.mediawiki b/317-Protocol.mediawiki index 9fafb24..0b97c20 100644 --- a/317-Protocol.mediawiki +++ b/317-Protocol.mediawiki @@ -437,7 +437,7 @@ The following is what most people think of when they say 'update mask' and 'upda Inside this method, many different bitwise masks are compared to the player's flag, and if the mask is set, logic is performed. These masks are frequently called update masks. A list of player update masks are below: -* '''0x400''' The 0x400 mask is used to update the player so they appear to be asynchronously animating and walking. +* '''0x400''' The 0x400 mask is used to update the player so they appear to be asynchronously animating and walking. This mask is often used for the Agility skill. The data associated goes in order of: byte (type C) which is the first location's X coordinate value, byte (type S) which is the first location's Y coordinate value, byte (type S) which is the second location's X coordinate value, byte (type C) the second location's Y coordinate value. After the locations are written, there is a required movement speed which is written as a short which marks how fast to move from position 1 to position 2. Another short (type A) is written as the movement speed going from position 2 to position 1. Finally one byte is written to end the mask block, which marks the direction. * '''0x100''' The 0x100 mask is responsible for player graphics updating. The data associated is a little-endian unsigned short which represents the graphics id, and an int which is the graphics delay.