So I am working on a project that is almost done. It has been a great learning experience for me and I am really excited about it. Before I can use it or test it or move it into beta or anything though, I need to know a few minor things about Lusternia. I am hoping these are not infringing questions and I hope that answering them will be easy enough.

1) Does Lusternia use TelnetGA (at all or, say, for prompts) ?

2) Does Lusternia use MCCP? MXP? Pueblo? All three?

3) Is it (I thought it was ATCP) that is used to capture the gauge data in transmission? (I swear there was a thread on it with Tiny Fugue and ATCP but I can't seem to catch it at all...)

4) For the coloured strings that are sent from the mud, what is that done with? Is it just string matching colours? (IE: $Newbie: or something?)

Thanks so much!

1. Yes.

2. MCCP.

3. ATCP, yes.

4. ANSI escape codes.

My Hero! !

2. I am 90% sure it also uses MXP and Pueblo.

Oh maaan.... for real?

Actually, I'm rather positive Lusternia doesn't use either MXP or Pueblo.

MXP is negotiated on connection. My client has MXP enabled because of some few odd things I do with it, but I've never seen MXP-style links or menus from Lusternia.

Pueblo is right out, as there is no connection negotiation to disable Pueblo server-side. The default is to disable it server-side, and you generally have to enable it through some command in-game. And then you see pictures and hear sounds and use a lot more colors than the standard ANSI 16 (0-15 in CONFIG COLOUR). Some MUDs don't disable it, so if you connect without Pueblo support enabled, you see a lot of garbage.

I just looked, and there's no reference to Pueblo anywhere in our in-game options that I could find.

Both tend to be selling points of MUDs that have them, so I would have expected to hear more about them if Lusternia made use of them.

MXP was created after Achaea started using ATCP. ATCP was made because something like MXP doesn't exit.

Mudbot will use MXP to do stuff, but not Lusternia.

Ok so just having ATCP and MCCP will be good. Many thanks all!

MCCP is bad. I don't use it, and I don't recommend anyone else use it, either.

I would agree. Unless you feel like adding in the feature, leaving out MCCP shouldn't make you feel guilty. It's great in theory, but does odd things.

So not having MCCP won't hurt the play of the game or triggering or anything like that? Hrm... ok then.

It's a compression protocol. Supposed to speed things up, especially when you get bursts of a lot of text, but in practice it's not so great.

Using ATCP and MCCP together can also cause problems, especially if whatever you're using it for uses the composer. Mudbot actually disables MCCP temporarily when the composer tries to start so that it receives the data properly.