opcodes not matching

[WillowyLady]

[03.16. - 12:24:55] [WORLD__CLIENT] New connection from 192.168.0.2:1579
[03.16. - 12:24:55] [NET__IDENT_TRACE] 192.168.0.2:1579: First opcode 0x7752 did not match expected 0x2792
[03.16. - 12:24:55] [NET__IDENT_TRACE] 192.168.0.2:1579: Tried patch 6.2_world, and it did not match.
[03.16. - 12:24:55] [NET__IDENT_TRACE] 192.168.0.2:1579: First opcode 0x7213 did not match expected 0x2ec9
[03.16. - 12:24:55] [NET__IDENT_TRACE] 192.168.0.2:1579: Tried patch 6.2_zone, and it did not match.
[03.16. - 12:24:55] [NET__IDENT_TRACE] 192.168.0.2:1579: First opcode 0x7752 did not match expected 0x4dd0
[03.16. - 12:24:55] [NET__IDENT_TRACE] 192.168.0.2:1579: Tried patch Titanium_world, and it did not match.
[03.16. - 12:24:55] [NET__IDENT_TRACE] 192.168.0.2:1579: First opcode matched 0x7213 and length matched 68
[03.16. - 12:24:55] [NET__IDENTIFY] Identified stream 192.168.0.2:1579 with signature Titanium_zone
[03.16. - 12:24:55] [WORLD__CLIENT] New client from 192.168.0.2:1579

Anyone able to explain whats going on with the opcodes not matching. It doesn't appear to have any effect on ability to log in and play.

Using Titanium, 384 and latest svn.

I am just curious::D

[Andrew80k]

The server tries to identify which client you are coming from. This is basically its way of saying you are using a Titanium client as opposed to a 6.2 client or a SoF client.