Question on Achaea's ATCP not working.

Posted by Faedara on Tue 18 Jan 2011 04:47 PM — 9 posts, 36,413 views.

Faedara Tue 18 Jan 2011 04:47 PM #0

Sorry if this is the wrong place or been asked before, but it seems to me that Achaea's ATCP has been either completely removed or simply stopped working for me. I know about this GMCP that Achaea's started but none of my plugins run on GMCP in the first place, including Nick's mapper...

Anyone have a general idea of what's going on, or should I delete everything and start over because it's a problem on my end?

Twisol USA Tue 18 Jan 2011 07:58 PM #1

If I connect to Achaea and look at the Telnet events it produces, I see this:

IAC WILL 25
IAC WILL 200
IAC WILL 201
IAC WILL 86

GMCP uses code 201, while ATCP uses 200. Above, it's offering to enable either one. If I enable ATCP and log in, I do indeed see a Char.Name message.

Can you paste the packet debug output from during login? (Please please please be sure to remove your password from the outgoing packet debug before pasting it here!)

Faedara Tue 18 Jan 2011 08:34 PM #2

Alright, I'll figure out how to do that and paste it here. Shouldn't be too hard at all

Twisol USA Tue 18 Jan 2011 08:39 PM #3

You can enable the debug output at Edit -> Debug Packets. Make sure your world window isn't maximized or the debugging window will be hidden behind it.

Faedara Tue 18 Jan 2011 09:02 PM #4

That's exactly how it came to me, looks a bit messy and hard to read, but I suppose you'll be able to read it better than me... So many numbers...... =.w.=

Let me know if I should clean it up, I'm pretty sure the pass and name are out, but the way it's broken up I can't tell if they appear more than once.

((Too large to post here, sorry if links are frowned upon))

Twisol USA Wed 19 Jan 2011 12:22 AM #5

We've determined that it's probably an issue with the mapper component of the Vadi system Faedara is using.

Faedara Wed 19 Jan 2011 02:24 PM #6

Well said Twisol, well said!

Larkin Thu 20 Jan 2011 05:25 PM #7

For the benefit of anyone else reading this later, I'll give a summary of the problem:

When you enable GMCP, you stop getting ATCP messages, and vice versa. Vadi's code all uses GMCP now, so it will block the ATCP, even if you try to enable it through your own plugin (because his system is a proxy and gets to reply before MUSHclient does).

Twisol USA Thu 20 Jan 2011 09:00 PM #8

I'm aware of that issue, but when we were diagnosing the issue, I had Faedara use the ATCP DEBUG alias of my plugin to display all ATCP messages being received, and she was definitely receiving ATCP messages. It's possible she just has an older version of the core executable or something.

The particular issue I noticed is that the Room.Info message wasn't being received if the vadi mapper module was active.