[Emp`]

You don't really need the cvar dr_enabled. You could just use dr_type for enabling/disabling.

You also don't need to cache whether it is enabled during plugin_cfg since you do it in client_disconnect anyway.

Additionally, disconnects do not happen that often, so it seems unnecessary to use static variables.

It is also unnecessary to create Version as a constant global since it is used only once. You should just use it as an argument in register_plugin.

Another thing you should be aware of is that you don't need to put in the color codes as hex values. Escaping the number by itself (ie. ^1 instead of ^x01) works fine.

As xPaw pointed out (and you agreed upon) you should just use MSG_BROADCAST. If the color code is still attached to g_iDisconnectID, you should use it for ewrite_byte so the name will show in the color of the team the player was on.

Last thing to point out is that you missed a semicolon on line 57.

Otherwise, good job with this.

[Bugsy]

Originally Posted by Emp` You don't really need the cvar dr_enabled. You could just use dr_type for enabling/disabling.

I could do that, heck, I could cram all options into a single cvar using bit flags. However, I prefer a separate cvar solely for enabled\disabled.

Originally Posted by Emp` You also don't need to cache whether it is enabled during plugin_cfg since you do it in client_disconnect anyway.

Thanks for noticing. I added the plugin_cfg() g_bEnabled assignment while testing and I left it in accidentally. I was calling SV_DropClient_Post manually and needed the bool value updated prior to an actual player disconnecting.

Originally Posted by Emp` Additionally, disconnects do not happen that often, so it seems unnecessary to use static variables.

Agreed.

Originally Posted by Emp` It is also unnecessary to create Version as a constant global since it is used only once. You should just use it as an argument in register_plugin.

I am aware I could plug the value into register_plugin() directly but I choose not to. I write all of my plugins with a separate Version constant all the way at the top under the includes. I prefer this so when I release a new version I just go to the top to make my increment.

Originally Posted by Emp` Another thing you should be aware of is that you don't need to put in the color codes as hex values. Escaping the number by itself (ie. ^1 instead of ^x01) works fine.

To be honest, my color chat function I obtained on the forums somewhere and I never bothered to modify how the values were laid out. Not that it matters which method is used, but relevant point.

Originally Posted by Emp` As xPaw pointed out (and you agreed upon) you should just use MSG_BROADCAST. If the color code is still attached to g_iDisconnectID, you should use it for ewrite_byte so the name will show in the color of the team the player was on. Last thing to point out is that you missed a semicolon on line 57. Otherwise, good job with this.

Thanks for the comments.

[Bugsy]

I posted a revised copy with corrections made. I will also update the signature as Arkshine suggested when I get a chance.

[Stressful]

Doesn't work for me . As there's this error . How do I solve it ?

L 09/03/2011 - 18:35:48: [ORPHEU] Function "SV_DropClient" not found
L 09/03/2011 - 18:35:48: [AMXX] Run time error 10 (plugin "disconnect_reason.amxx") (native "OrpheuGetFunction") - debug not enable

[Arkshine]

Show the output of orpheu parsing the config file at server start. (server log)

[MostwantedScript]

Great idea! By the way did you get this idea from sa-mp?

[drekes]

Originally Posted by MostwantedScript Great idea! By the way did you get this idea from sa-mp?

Originally Posted by Bugsy Made by request.

Nice work Bugsy

[MostwantedScript]

my fault

[.:cs.stambeto:.]

Nice plugin!

[xPaw]

You should check if g_iDisconnectID is greater than 0 in SV_DropClient. It happened once that it printed server name.

P.S. I edited it to remove checks, so it prints all disconnect reasons, and works quite ok.
EDIT: Forgot to say that it works on linux.