Question from yuki [About Client]

[Syst3m_W1z4rd]

how to get the client version from a connected client

Don't ask me why, I don't know ><

[Kiyono]

So why doesn't he ask it himself...?

[Basser]

AFAIK, the client does not does send a packet containing the client version, so I doubt it is possible to get it any other way than modifying the client or doing something different client sided. I am not entirely sure it cannot be found in any packet though, 'cause if I remember correctly, 'The Warlords' (another TQ game) does send the client version in one of their authentication packets.

[Syst3m_W1z4rd]

Originally Posted by Kiyono

So why doesn't he ask it himself...?

his banned and havent made a new account, so he asked if I would put the question

[Kiyono]

Originally Posted by Basser

AFAIK, the client does not does send a packet containing the client version, so I doubt it is possible to get it any other way than modifying the client or doing something different client sided. I am not entirely sure it cannot be found in any packet though, 'cause if I remember correctly, 'The Warlords' (another TQ game) does send the client version in one of their authentication packets.

TQ did have some way to check for the client version, if you take a look at the actions table, you'll see that the mystic merchant script used something to determine the clients version.

[-impulse-]

when client connects it sends server name to the server...just change the name of the server from server.dat to the version and you are done

[Korvacs]

They added it once to encourage people to update the client and immediately removed it once people started abusing it, it was sent in the auth request packet somewhere i think.

[InfamousNoone]

Inject a DLL into Conquer.exe
Have this DLL hook the auth-creation packet (the one with user,pass,etc)

Now assuming your running like 5095/+ the packet for this is HUGE.
You have a 128-byte field dedicated the name alone! So,
have your DLL insert the version # (read from version.dat) into the auth packet.

Process the version serverside -- good2go.
I'd recommend including a checksum unike TQ so people don't abuse it, lol.

[|NeoX]

Basicly the cleint doesnt send its version to the server... so i can quit the idea of making an InterServer for 1.0 - 2.0

I wonder how you did that Hybrid.

Is there a way to "Guess" the version based on the incoming client packets?

[Basser]

You could analyze all received data and try to 'reason' the version, however that would be very inaccurate.

[Korvacs]

The best you could do was analyze the auth packet and determine based on its structure which range of client was incoming as bas says this would be fairly inaccurate, you wouldnt be able to see the difference between specific clients, just the ranges 4267/5017/5165/5200 etc, atleast thats probably the best you could do without dll inject as inf suggested.

[|NeoX]

i might just figure out wich packets changed on each patch, so allowing to "scan" the client packets and then guess a version.... sounds like Client Close to me at this point

EDIT: The Auth Stage gets skipped. so i would need to do it at MapShow

DataPacket - 74

Maybe its possible to determine the clientversion at HotKey or Inv - Confirm and that stuff.

[Korvacs]

Originally Posted by |NeoX

i might just figure out wich packets changed on each patch, so allowing to "scan" the client packets and then guess a version.... sounds like Client Close to me at this point

EDIT: The Auth Stage gets skipped. so i would need to do it at MapShow

DataPacket - 74

Maybe its possible to determine the clientversion at HotKey or Inv - Confirm and that stuff.

No, it has to be done at auth because the chat packet which is sent to the client at the beginning of the game login process changes everytime the client is changed.

[|NeoX]

I see... goodbye easy way.

Thanks. can be closed^^

[|NeoX]

I see... goodbye easy way.

Thanks. can be closed^^