Is it possible to find out which players were already spawned before script was connected to the server?

It's like I have a server with 3 players: first one is driving around, second is spawned but hasn't moved or received any damage and the last one is still selecting his team. And now when I connect mIRC script, it should get every player's state - if he is spawned. How to do that?

Checking the hp or coordinates won't work (2nd player).

EDIT: btw it's enough with the idea how to do that; the mirc script is not so important

Hello!

I'm trying to create an rcon client that's using the rcondll.dll (I don't want to learn the r.a.k.n.e.t yet) and I've got a problem with receiving messages from the dll. I can connect to the vc:mp server, send commands (for example, "kick 0") and disconnect, but I don't receive any rcon output (like "[join] 0 Player" or "RCON: Kick Usage: kick <playerid>").

To send something back to the mIRC it should create a mapped file named "mIRC", copy all the commands to this file, and send a Windows message WM_USER+200 (or 201) to the mIRC. When mIRC receives this kind of message, it reads commands from the mapped file and deletes the file. (This information is from the mIRC's help)
But my application doesn't receive any WM_USER+200 or +201 messages from the dll, while it does from other app`s. So maybe the problem is with the window's handle - rcon.dll sends messages to some other (wrong) window.

dll has a function inside that creates mapped file and sends the message, so it must be using the way described in mIRC help, but I don't know how it obtains the handle of the target window - ways I can think of are:
- it can search for a window with certain ClassName, FileName or Title;
- it can use the hwnd parameter passed through RconConnect function;
- it can use the hwnd variable from the LOADINFO struct ( used in LoadDll function ).
- it's using GetProcessWindowStation and GetUserObjectInformation functions (I'm not sure why?)
But maybe there is another way that I haven't thought about!?

In the end - can you tell me how the .dll gets a handle of the mIRC window??

.