[EFFx]

Dude, he's from USA. If he told that it's correct who'll be against him? A person from 'Street'?

[Bugsy]

Lol, really? Its proper English, chief. Google "I can't imagine" if you don't believe me. It's basically saying "I cannot think of a reason why."

Back on topic.

[Schopenhauer]

It's not working. Unapproved

[Bugsy]

Just tested

[georgik57]

Can this be done somehow without Orpheu or any other extra module?

I was thinking about hooking the console print sent to the players "X has left the game", but don't know how to do it.

[Bugsy]

Do you care how/why the player left? If yes then nothing out of box detects why the disconnect happened.

[georgik57]

Originally Posted by Bugsy Do you care how/why the player left? If yes then nothing out of box detects why the disconnect happened.

No, not really. I just need a fix to cover all disconnect cases in AMXX 1.8.2 without any extra modules.

But if what I said can be done, the same can be done with the previous same type message(X dropped/timed out, etc) which is printed before "has left the game".

[Bugsy]

I don't know how you can differentiate a time out, kick, graceful drop without a non OOTB module.

[georgik57]

Originally Posted by georgik57 I was thinking about hooking the console print sent to the players "X has left the game"

[Bugsy]

But that does not tell you why, right? May as well use client_disconnect(). There will always be a delay when a player times out and when client_disconnect() gets called because the game does not know he is gone until he fails to respond for a certain interval -- just the nature of the UDP protocol. I tested this recently and IIRC, it was ~1 minute.