Has anyone started actively using GMCP yet? I'm having problems getting it to work as I expect it to, so I'm not sure it's a bug or just me...

I'm testing a plugin with parts of GMCP, but I'm not actively using it, still relying mostly on ATCP.

(Probably should put this in Mechanic's Corner.)

That's actually one part that I'm having problems with... I can't get ATCP and GMCP to cooperate. Whenever I add GMCP, ATCP stops working altogether.

Also, are you using Comm.Channel at all? Whenever I try using it, it gets a nervous breakdown more or less.

EDIT: Oh, and feel free to move it if anyone is able.

I'm using the Room, Vitals, and Items functionality, not the Channels stuff yet.

And, I have no troubles using ATCP and GMCP at the same time in separate plugins.

Not sure how does Larkin accomplish that because if you enable GMCP, ATCPs gets automatically disabled. So you're doing nothing wrong, Ssaliss.

Rapture feature!

I must've been mistaken and just not noticed because my GMCP picked up the slack. Sorry for the misinformation!

Good to know. Although it means I'll have to rewrite everything at once, and not just part of it at a time.

Also looking forward to them fixing the bugs in the Comm package...

I don't understand the Comms bug you've mentioned. What exactly is your issue with it? Is it a protocol error or just a misunderstanding of how to implement it properly in a client?

Well, first, when I activate it it gives me a ton of "I cannot fathom your meaning." messages. In addition, at least our CT is rather bugged, in that it doesn't generate the correct Comm.Channel.Start and Comm.Channel.End messages for everyone but me. When I use it it generates a whole bunch of them though.

Hmm. I've seen the "what are you trying to do?" messages myself, but I hadn't thought of GMCP as the culprit yet. I just figured one of my combat system scripts was sending hidden commands and I couldn't figure out what or where. I'm not using the Comm stuff, either, so that's odd, too.

I'm currently testing with this:

Yeah, that's another bug with it. I don't know which of the packages does it, but one of them adds Comm as well... Haven't bothered trying to figure out which of them.

Yeah, the ton of invalid commands at the beginning is an GMCP thing. Reported quite a while ago.

Reported it as well. It only seems to be isolated to the Comm package though; I haven't see it happen with any other packages.

I tested it more after you said that the Comm stuff enabled itself no matter what, and I found that even if I only asked for Char.Vitals, it turned on just about everything. I don't think it's really handling the Supports messages properly.

Yep!

GMCP is a wonderful thing.

I've noticed similar things, but never tested it thoroughly. After some further tests, however, it seems the list isn't always initially empty, as you might expect (although it often is). As such, even if I just initialised the GMCP protocol without adding any packages, it still gave me data. I think sending an initial Core.Supports.Set fixed the problem though; now I seem to get all the correct packages without hassle. Of course, I always just use Core.Supports.Add, so it shouldn't apply if you use Core.Supports.Set all the time.

I'm using Add, too, so I suppose Set solves this one issue, at least. I was figuring that you always logged in with nothing active and could Add/Remove during that one session. Apparently, it saves your options between sessions.

It doesn't even do that, it seems. I got different modules activated during different sessions when I tested it.

I too use gmcp and it's pretty cool. I get the miscommand line spam at first login but that's it. I assume that's what you're talking about?

Partly, yes. That's when you activate the Comm module. There are a few other bugs as well.