|
||
|
|||||||
| PlayUO (Krrios' Client) Support & Etc for Krrios's UO Client. |
![]() |
|
|
Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
Join Date: Sep 2002
Posts: 15
|
KUOC doesn't work on any UO server* which has fastwalk detection implemented the same way as OSI. What happens, you ask?
1) KUOC continually complains about getting packet 0xbf sub 0x02 while walking. 2) The server reports the KUOC client as sending corrupted fastwalk keys. 3) OSI clients work fine. 4) What do you think happens when the server gets a shitload of corrupted fastwalk keys from a client? Heh. * = Well, okay, I only know of one that has this. Haven't checked the various UOX spinoffs, or POL, or Sphere for it. |
|
|
|
|
|
#2 (permalink) |
|
UO Gamers: Demise Administrator
Join Date: Oct 2002
Location: Swamp
Age: 29
Posts: 10,816
|
Hrm... I have the default RunUO fastwalk detection on my shard, and the KUOC has no complaints.... Then again, I don't know what you mean by "implemented the same way as OSI" :->
__________________
psz Demise' Creator (Retired) The RunUO.com Forum Moderator Team Former Official RunUO Scripter (Retired) Websites: My 360 Blog My Gaming Site(Old Link) My Gaming Site(New Link) |
|
|
|
|
|
#3 (permalink) |
|
Join Date: Sep 2002
Posts: 15
|
I mean using the four bytes in the 0x02 (move) packet for a current fastwalk stack key (when sending movement requests to the server), as well as supporting & handling 0xbf subcmd 0x01 and 0x02, one of which is the fastwalk init packet, and the other is the 'add fastwalk key' packet. Both those 0xbf subcmds are only sent by the server to the client, not vice versa.
I'm not using RunUO. |
|
|
|
![]() |
| Bookmarks |
| Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
| Thread Tools | |
| Display Modes | |
|
|