Ping

Is there anyways to check users ping serverside? If I'm right ping is getting handled by the client and the ping packet just requires you respond back, but is there a way you can check the ping at the server?

Never tested it myself, BUT it might actually contain the ping.

Breakpoint the data you receive upon the packet being handled, check the values.

Not really... You could try to keep track of the system time on the client's machine but it would be quite ineffective and resource intensive...

Alternatively you could find a packet that the client responds to and send it and time how long it takes to get a reply... but again, there's no simple way to do it.

Quote:

Originally Posted by pro4never Not really... You could try to keep track of the system time on the client's machine but it would be quite ineffective and resource intensive... Alternatively you could find a packet that the client responds to and send it and time how long it takes to get a reply... but again, there's no simple way to do it.

Yea, that was what I was thinking as well. Not like it's something important, was just wondering.

Quote:

Originally Posted by pro4never Not really... You could try to keep track of the system time on the client's machine but it would be quite ineffective and resource intensive... Alternatively you could find a packet that the client responds to and send it and time how long it takes to get a reply... but again, there's no simple way to do it.

MsgTick (1012), it checks for a valid session and if the client doesn't answer correctly or in a valid time range, the client is disconnected. But in general, private servers don't have this packet.

Else, there is an action for MsgAction (1010) that the client need to answer directly. It's like a bot check or I don't know. (Action: 100) The param is the client's timestamp.

I really don't think packet 1012 is necessary. I think it's completely useless. If it's a fake client, they'll just code it in anyways.

Quote:

Originally Posted by Fаng I really don't think packet 1012 is necessary. I think it's completely useless. If it's a fake client, they'll just code it in anyways.

It can be interesting to flush bad client with too high ping... But yeah, in fact, it's useless for a bot check, but anyway, it's not the first function of the packet. The hash method can be a little verification, nothing more.

Quote:

Originally Posted by Y u k i PHP Code:  bool fSend = false;             try             {                 if (fSend = Monitor.TryEnter(this, 50))                 {                     this.Socket.Send(Packet);                 }             }             finally              {                 if (!fSend)                     FailedSend();                 else                     Monitor.Exit(this);             }  thats how ive seen it. Doesnt rly check the ping but on laggy connections it will drop the client.

By doing a search on my current interest, I couldn't help it notice that what you said here is wrong. The function Socket.Send will just buffer your data in the underlying system to be sent and will not also wait until the data is delivered.

Quote:

Originally Posted by -impulse- By doing a search on my current interest, I couldn't help it notice that what you said here is wrong. The function Socket.Send will just buffer your data in the underlying system to be sent and will not also wait until the data is delivered.

The code is from Hybrids Send method lul.

Packet 1012 is NOT useless; it displays the "warning: network is congested" message for laggy clients. Implement if you're a perfectionist like me.

Quote:

Originally Posted by Lateralus Packet 1012 is NOT useless; it displays the "warning: network is congested" message for laggy clients. Implement if you're a perfectionist like me.

Conquernist. :rolleyes:

Quote:

Originally Posted by I don't have a username The code is from Hybrids Send method lul.

That Monitor.TryEnter is for locking purposes. If the server can get a lock for 50 ms on the client's class it will send the packet otherwise it will disconnect the client so no important packet can be lost. Once the lock is gone it's no problem, though it wont take more than 1 ms to use the Send function.

Quote:

Originally Posted by -impulse- That Monitor.TryEnter is for locking purposes. If the server can get a lock for 50 ms on the client's class it will send the packet otherwise it will disconnect the client so no important packet can be lost. Once the lock is gone it's no problem, though it wont take more than 1 ms to use the Send function.

I know already lol.

Why you pushed old theards?

And he is banned !

Reported

Quote:

Originally Posted by நெல் Why you pushed old theards? And he is banned ! Reported

I'm not banned on this account umad? And because someone had something related to the topic.