Brief summary of issue / Description of requested feature:

Configurable auto-connect behavior to allow for connecting to servers that require credentials in a different format. Specifically, LambdaMOO servers which expect co <user> <password> (or connect <user> <password>).

Steps to reproduce the issue / Reasons for adding feature:

1. Create a profile for a LambdaMOO server
2. Input username and password
3. Try to connect and receive errors rather than being logged in.

Error output / Expected result of feature

Error output (from server):

I don't understand that.  Valid commands at this point are
   WELcome, Who, COnnect, CReate, Quit, UPtime, Version, REQuest, or Help
I don't understand that.  Valid commands at this point are
   WELcome, Who, COnnect, CReate, Quit, UPtime, Version, REQuest, or Help

(first when the <user> string is sent, and then again when <password> is sent.

Expected behavior:

co <user> <password> sent so that I can be properly logged in to the MOO.

Extra information, such as Mudlet version, operating system and ideas for how to solve / implement:

(Edit: Experiencing this issue with Mudlet version 4.9.1 on macOS)

Per @demonnic, it sounds like there may already be some ideas floating around about how to revamp the connection phase, possibly making the <user> and <password> available as variables so they can be used in custom triggers. Making this configurable rather than providing a fixed set of options seems like it would provide the most general fix that could also apply to other servers which may have yet different expectations about what a client should send to authenticate.

My own immediate need, however, is just for the ability to send:

co <user> <password>

Thanks!