It works like this:
IF client uses Razor AND has the negotiate feature enabled, it will react to a 0xF0 packet from server. The packet is:
BYTE[1] 0xF0
BYTE[2] length (0x000C)
BYTE[1] 0xFE
BYTE[8] features to disable (for respective OR-ed values see this RunUO script )

If you have Razor running, it ...

Are you sure the mount has a backpack? The command .openpack creates a new one in case the mount has no backpack, so it is not a good way to check.

Here is the flaw:
Imagine you have negative z, like -1. As I explained above, signed variables have different bit structure.
Hex(-1) will give 0xFFFFFFFF. You are trying to write this into 1 byte, which invokes your failsafe condition and returns nothing. What happens next, I am not sure, but I ...

I think the problem is in the function ConvertIntToHex, could you post it here, too?
Also, I recommend using Packet functions instead of building a string, it is much cleaner.

I think we will need more information on this. Can you copy the malfunctioning script here?

However, I suspect what the problem is. While working with packets, do you have anything like this in the code?


packet.setInt8(position, player.z);


The z coordinate goes from -128 to 127 and therefore ...

Okay, thanks, here's why I think it should be fixed. In eScript many error catches are done by error propagation, like in this case:

if (GetSomething(someone).getprop(some true/false parameter))
do something
endif
If there is something wrong with the input, something doesn't exist, the result is ...

If the client has "Query before performing criminal actions" turned on, the Cursor type returned is 0 in cases where the player had to go click through the criminal query. That means if you send either harmful or helpful cursor to the client, there is no guarantee it will send back the same ...

Hi, if I compare an error with a number (SendSysMessage(me, CStr(error < 1))), the result is random, sometimes 0 and sometimes 1. I would expect the result to be an error or zero.