Iris2.de

just stumbled upon yet another very ugly uo hack...

# uo-protocol change for clientversion 6.0.1.7 and later : 0x08 kPacket_Drop_Object is now one byte longer

there seem to be other protocol changes as well,
i made a wiki page for listing info on this :

http://iris2.de/index.php/Clientversion ... _and_later

i made a function ClientVersionIsPost6017() that can be used to check which version iris reports to the server, so we can later add the protocol changes to our code using it,
but until those changes are coded in iris, the maximum version that iris supports is 6.0.1.6

i also added a check at startup that prevents iris from launching if a higher version string was configured, as iris would loose sync with the server after the first changed packet was sent or received.

I'm writing my own packet based UO scripting tool and here are a couple more observations I've made regarding client 6.0.1.7+:

packet 0x25 is also 1 byte longer.

the loop in packet 0x3C is also one byte longer. However, servers will occasionally still send an old style 0x3C packet to a a newer client. Loop size for new packet is 20 bytes, old is 19. So the safest thing is to check (packet length - 5) % 20, and if you get zero you know it's a new style packet.

in the meantime we added support for 6.0.1.7 and later,
here's the changeset if you're interested :
http://zwischenwelt.org/trac/iris/changeset/2900

for 0x3c we don't check the packetsize so far, i might have to still add that. *busy coding at it*

done =)