ID:142391
Jun 11 2008, 5:02 pm (Edited on Jun 11 2008, 5:14 pm)
|
|
Edit - Done it a different way and it works fine now.
|
In response to Jeff8500
|
|
Jeff8500 wrote:
No usr in procs.* That doesn't help at all, and there is no usr in there. |
In response to Howey
|
|
Read the ref. There is a usr there.
In fact, just read his entire post. He explains what's going on right in it. |
In response to Popisfizzy
|
|
Popisfizzy wrote:
Read the ref. There is a usr there. ...No there isn't a usr there... I wrote it, I know there isn't a usr there... |
In response to Howey
|
|
It doesn't matter, I did it a different way and it's working fine.
|
In response to Howey
|
|
No, see, read the freaking ref. We tell you that for a reason. There is a damned usr there.
//From the reference. There is a god damned usr in that proc, like we told you. I told you to check the ref; I told you to check his post; don't be thick when we tell you to check something. We know what we're doing and you don't. If you knew what you were doing, chances are you wouldn't be here. Either quit being thick or find another place for help. |
They already have a mob by the time you ask for the pass, but it doesn't matter because they'd see world messages as just a client also. Just send world message to the clients list and only add clients to the list after they have supplied the password. Of course, the reason you're not getting the input() is probably because it's sent to usr by default, you want src here.
#define PASS "eggs" |
In response to Popisfizzy
|
|
holy crap lol its not lyk he is blind lol you commented it a bit too much there.
|
*input defaults to usr.