|
Mushclient also correctly identifies it and several glitches that existed in negotions have been corrected in recent versions. There is even an option you can turn on to convert certain codes, which some muds use to indicate a prompt, into a "newline+charage return" as they arrive, so the client actually sees a prompt. Other clients get around this I believe by keeping the current 'state' of the input and matching on partial lines, which haven't terminated. I'm not sure if I agree with the reasoning of that allowing this, except that you can't do:
Match="You see a red bunny", sequence=1
Match="You see a *", sequence=2
And avoid having the second one match on a partial line, even when it should only match the first one. While there are obviously solutions to this, Nick chose to simply only deal with lines that end with /n/r.
Anyway, sorry for the side track, but I think most clients do respond to the client ID sequence, but I might be wrong.
|