it was time for an update of the 2 other plugins, I will try your plugin right away.
Deadchat 1.3 was creating hundreds of such error lines in my error logs:
L 11/05/2011 - 00:08:00: SourceMod error session started
L 11/05/2011 - 00:08:00: Info (map "de_nightfever") (file "errors_20111105.log")
L 11/05/2011 - 00:08:00: [SM] Native "StartMessage" reported: Unable to execute a new message, there is already one in progress
L 11/05/2011 - 00:08:00: [SM] Displaying call stack trace for plugin "deadchat_cstrike.smx":
L 11/05/2011 - 00:08:00: [SM]  Line 201, /groups/sourcemod/compiler-1.4/include/usermessages.inc::StartMessageOne()
L 11/05/2011 - 00:08:00: [SM]  Line 242, /home/groups/sourcemod/upload_tmp/phpGUp19i.sp:rintGameChatMessage()
L 11/05/2011 - 00:08:00: [SM]  Line 156, /home/groups/sourcemod/upload_tmp/phpGUp19i.sp::SayText2PostHook()
L 11/05/2011 - 00:22:40: Error log file session closed.
Do you know what does it come from?
And could it be fixed? I asked on the thread but I had no answer
I liked the deadchat_teamsay binary of this plugin.
If set to 0, dead players can NOT talk with their alive teammates without being read by enemies (by using say_team command).
If set to 1, dead players can talk only with their dead AND ALIVE teammates without being read by enemies (pressing "u", by default), allowing them "ghost chatting" to give indications like "they are in bombsite B" or so...
Of course it's better to play with deadchat_teamsay 0. This way when they press u, deadplayers only talk with dead players of their team (like if plugin was disabled).
Anyway I'll try yours and give feedback.