Differences

This shows you the differences between two versions of the page.

--- uo_protocol_0xbf [2014/07/17 17:01] – created thooge
+++ uo_protocol_0xbf [2014/07/17 17:07] (current) – thooge
@@ Line 27: / Line 27: @@
     * 11 - Client language
     * 12 - Closed Status Gump
+Server Message. This sets up stack on the client and whenever it moves, it takes the top value from this stack and uses it. (key1 start at the top, key6 at the botton).
+==== Subcommand 1 - Initialize Fast Walk Prevention ====
+bytes (for 29 total)
+<code>
+BYTE[4] key1
+BYTE[4] key2
+BYTE[4] key3
+BYTE[4] key4
+BYTE[4] key5
+BYTE[4] key6
+</code>
+==== Subcommand 2 - Add key to Fast Walk Stack ====
+bytes (for 9 total)
+Server message. This key is added to the top of the stack. In other words, it's the one that will be used next. Basically, the other 5 only get used when the client is sending moves faster than the server is responding.
+<code>
+BYTE[4] newkey
+</code>
+==== Subcommand 5 - Unknown ====
+bytes (for 13 total)
+Client Message.
+<code>
+BYTE[4] unknown (00 00 03 20)
+BYTE[4] unknown (00 00 00 05)
+</code>
+==== Subcommand 6 - Party System ====
+YES! Subsubcommands
+Party system is implemented as subsubcommands.
+<code>
+BYTE subsubcommand #
+</code>
+=== Subsubcommand 1 - Add a party member ===
+(4 bytes)
+Client Message.
+<code>
+BYTE[4] id (if 0, a targeting cursor appears)
+</code>
+Add party member(s) (1+ numMembers*4)
+<code>
+BYTE numMembers (total number of members in the party)
+Then, for each member in numMembers:
+        BYTE[4] id
+</code>