Post: #2

this new packet works in the same way as the default walk packet but it also have some internal fastwalk prevention checks, but there's no advantage to enable it, this fastwalk prevention doesn't work well so this packet is useless. All the others UO emulators still using the old packet too, and they doesn't even added support for this new packet

sphere already have its internal fastwalk prevention engine (EF_FastwalkPrevention), which I think it's more reliable because all checks are on server-side without need to sync client/server timing, send packets, etc. But EF_FastwalkPrevention only works on linux because these checks will require an OS that have high precision timing calculation at kernel level, which linux already use it by default but windows doesn't use it (maybe only windows server?)

anyway, can you tell the X,Y,Z coord of this region where you can't walk? I'm also having this same problem on many map5 regions and need more info to track this issue