Client info - POL096.1-2006-07-02

[Repsak]

I found it odd that the core never had any clientinfo, so I hooked the packed to try and find out the problem.
Aparently the package is never send from the client in the first place.

Tested with client 5.02g, with uoexpasion 'AOS'

Did I miss something, or sis I hook the packet wrong?

Code: Select all

Packet 0xD9
{
  Length variable
  ReceiveFunction clientinfo:HandleClientInfo
}

Code: Select all

use uo;

program ClientInfo()
        Print("PacketHooks - Client Info" );
	return 1;
endprogram

exported function HandleClientInfo(who, byref packet)

        who := who;
        packet := packet;
        
        Print("who: " + who.name );
        Print("packet: " + packet );
        
	// Return 0, to let POL process the packet too.
	return 0;
endfunction

[Pierce]

Windows or Linux? On windows you receive the packet sometimes not on every login. There was a topic on that issue before. On linux core that won't work imho. I wish it would

[CWO]

The client sends it only once in a long while. Its in the Windows Registry when it last sent it.

[Repsak]

Its running on Windows.


Ahh, true, I completely forgot about the delay, ill try that one out.

[Repsak]

There are for sure something wrong with the clientinfo in the current pol (96.1).
I hooked the packet 0x9d to see what happens, but I found out that I had to use packet length 268, insted of variable for the hook to catch anything. (the UO-packet sniffer was a great help)

Here is the result from the console.

who: error{ errortext = "Object does not support members" }
packet_0x9dd90243c93c69000000050000000100000a28020000000f00000002000007070100000
200000004000000030000000010000900004d006f00620069006c006900740079002000520061006
40065006f006e0000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000100200004c590000002000020
610640061006e0000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000
Client disconnected from 10.0.0.21 (0 connections)
Client connected from 10.0.0.21 (1 connections)
syslog [scripts/misc/logon.ecl]: No ClientInfo 'Repsak' [reppy]

As you can see the 0x9D packet is send, but no clientinfo is detected in logon.ecl

The packet was send to the server at first connect, before you select character (proberlly why 'who' is an error)

[atreiu]

shard of my friend use old clients 2.0.0. 4.0.3
i didn't see any 0x9d at all from that clients not by server hook not by sniffer.

is it old clients for that packet and if yes then from what client version 0x9d packet start sending to server?

[ThisIsMe]

shard of my friend use old clients 2.0.0. 4.0.3
i didn't see any 0x9d at all from that clients not by server hook not by sniffer.

is it old clients for that packet and if yes then from what client version 0x9d packet start sending to server?

Bit of a necro eh?

I will tell you regarding this packet, the clients used on the shard that Repsak was the developer for still runs under 096 and uses this packet hook to grab client info. You will not get a response from Repsak likely as he has long been gone from developing for Pangaea.

In terms of what clients send and do not send 0x9D, this I can not tell you other than the 5.x.x.x clients send it and up.

[CWO]

You guys realize that the packet is 0xD9, not 0x9D....

[atreiu]

yeh its mistypo, i meant 0xD9

Code: Select all

Packet 0xD9
{
  Length 268 variable whatever
  ReceiveFunction clientinfo:HandleClientInfo
}

Thanks i'll try on modern clients

[ThisIsMe]

Hehe, cwo, I didn't even look because I know the shard the original op worked on uses this packet, as a long time player and now staffer.