Chat plugin in Medievia

Posted by Aduial on Sun 04 Apr 2010 11:28 PM — 21 posts, 73,842 views.

#0
Hi there.

I'm a long time MUSHclient user but have generally stuck to one mud. Recently I've been trying to use the chat plugin in Medievia (which works just fine in the other mud I play). However, somehow MUSH won't recognize the chat commands. They go straight to Medievia and the mud attempts to execute them as in-game commands.
I'm not sure if I'm just missing some setting. I have the chat plugin enabled in the Medievia world. I'm using MUSH 4.40. Any suggestions or questions are welcome!

Cheers!
Australia Forum Administrator #1
You might need to turn off the speedwalking prefix in the commands configuration. That defaults to "#" which will interfere with chatting.
#2
It was off already. I deleted the character anyway for good measure, but it still doesn't work. I also checked for aliases or etc, but no luck.
Australia Forum Administrator #3
Try turning on Game menu -> Trace.

See if that clears anything up.
#4
Nope :/ It doesn't tell me anything.
Australia Forum Administrator #5
Which chat plugin did you install? There is an older one and a new one called Lua_Chat.xml (should be in your plugins folder).

If you have that installed, and enabled, then something should happen. What chat command specifically did you try?
#6
I had:
<plugin
name="Chat"
author="Nick Gammon"
id="753ba7e011f3c8943a885f18"
language="VBscript"
purpose="Support for chat feature"
date_written="2003-04-13 14:32:22"
date_modified="2003-05-01 09:55"
requires="3.37"
version="1.3"
>

I imported lua_chat and enabled it (in Plugins, it says Enabled - Yes). I now have this one:
<plugin
name="Chat"
author="Nick Gammon"
id="03ca99c4e98d2a3e6d655c7d"
language="Lua"
purpose="Support for chat feature"
date_written="2005-12-18 07:32:00"
date_modified="2005-12-21 13:26:00"
requires="3.72"
version="1.0"
>

Still no results, here's a log:

[sfilmpqvw] <714/714hp 849/849m 610/610mv 100br 0xp -r>
chat:help
Thou must be confused.

[sfilmpqvw] <714/714hp 849/849m 610/610mv 100br 0xp -r>
#chat call
Thou must be confused.

[sfilmpqvw] <714/714hp 849/849m 610/610mv 100br 0xp -r>
#chats
Thou must be confused.

Sorry to be a pain, I just really want this to work :/
Australia Forum Administrator #7
Can you check in the aliases configuration, that aliases (in general) are enabled? It is a checkbox in the list of aliases.
#8
Ack! I had aliases disabled thinking something from there might be interfering! It works now, thank you :)
Now I'm having trouble chatting the password to the server. I know it's right since it works from another client.

Calling chat server at etc port etc
Session established to etc.
Chat session accepted, remote server: "wrath"
You have 15 seconds to chat your password to me.
#chat wrath mypass
You chat to wrath, 'mypass'
Incorrect...
Chat session to wrath closed.

My chat name is correct.

Any tips?
Australia Forum Administrator #9
Can you compare, if possible, exactly what the other client sends? Does it use double-quotes for example?
#10
I connected through MudMaster and chatted the password, I could notice it had single quote marks as well before it crashed (seems to happen just about every time I try to run it). Now I need to wait until tomorrow to be forced to authenticate again. I'll make another post copy/pasting then.
#11
Here's a log from Mudmaster:


<CHAT> Connection to wrath at rixak.com:1212 accepted.
You have 15 seconds to chat your password to me.
/chat wrath mypass
You chat to wrath, 'mypass'
Welcome to MMChat by Dirocus
Chat to the server 'help' for usage information

MMChat by Dirocus. Version:4.3.2

[wrath] septienna Has Joined channel Main (Connect:Password Auth)


Same chat name, same pass.
Australia Forum Administrator #12
I would have to guess that the MMChat thing is also checking colours. MUSHclient also sends codes for bold, cyan, the message, and then red.

Now if MMChat is very specific about the order (eg. cyan before bold) then that would throw it out.

If we know the exact codes that Mudmaster is sending, or the exact way that MMChat is checking, we can send the same things.
#13
Ah, so because the server is being hosted on a MudMaster and its chat I can connect through that but having trouble with MUSH. Blech. Is there any way I can check what you mentioned?
Australia Forum Administrator #14
Yes, but be prepared for a bit of work. :)

  • Download WireShark:

    http://www.wireshark.org/
  • Install it
  • Assuming you are using the default chat port of 4050, enter this into the Filter line:

    
    tcp.dstport == 4050
    

  • Click the Apply button next to it (see screenshot in next post). That should limit what would otherwise be a lot of data to things you send to port 4050 somewhere.
  • On the Capture menu, click Interfaces, choose the one that looks like it is connected to the Internet (if there are more than one) and click the Start button.
  • Fire up MudMaster and connect to the chat session. You should start to see stuff scroll by in the WireShark window.
  • Once you get asked for your password, enter it as normal.
  • Before doing anything else, check the Wireshark window. The last (or maybe second or third last line) should be the packet with your password in it.
  • Find the one where it says "Aduial chats to you, 'mypass'" (there will be extra stuff there which is the colour codes).
  • In the middle part of the screen (see screenshot) click on the Data line, which will highlight the data part at the bottom as in the screenshot.
  • Type into a forum message exactly what you see on the RH side (the text side), changing your password only. eg. For me it would be:

    
    .. Azeral chats to you, '.[1m.36mmypass.[31m'..
    


    Where "mypass" replaces the actual password.

    The parts about [1m.36m tells me the colour codes it is sending.
  • Close down Wireshark.

Australia Forum Administrator #15

See previous post.

Amended on Thu 08 Apr 2010 07:30 AM by Nick Gammon
#16
Okay, so here is what I got copy pasted, as well as a screenshot (it doesn't quite look like you predicted):


0000  00 24 17 7a 4d 70 00 22  fa 18 76 3c 08 00 45 00   .$.zMp." ..v<..E.
0010  00 49 06 40 40 00 80 06  ec 7d c0 a8 01 43 44 28   .I.@@... .}...CD(
0020  01 de ea a2 04 bc 24 7a  c3 5c 3b 02 4d 40 50 18   ......$z .\;.M@P.
0030  43 d2 be ed 00 00 05 73  65 70 74 69 65 6e 6e 61   C......s eptienna
0040  20 63 68 61 74 73 20 74  6f 20 79 6f 75 2c 20 27    chats t o you, '
0050  xx xx xx xx xx 27 0a ff                               mypass'.. 



There was nothing special about the pass I blacked out, it was plain text just like above.
Amended on Fri 09 Apr 2010 04:06 AM by Nick Gammon
Australia Forum Administrator #17
Blank out the hex codes on the left (on Imageshack), you can work out your password from that. I've done it to your posting. It might be wise to change your password now.
Amended on Fri 09 Apr 2010 04:05 AM by Nick Gammon
#18
Thanks, I changed it.
Did that help at all?
Australia Forum Administrator #19
Yes, that helped. Well it seems there were *no* colour codes. lol

This alias should solve your problems:


<aliases>
  <alias
   match="chatpass"
   enabled="y"
   send_to="12"
   sequence="100"
  >
  <send>
ChatMessage(ChatGetID ("wrath"),   -- who to
       5,   -- personal message
        "septienna chats to you, 'mypass'" ..   -- the message
       string.char (10)   -- newline
       )
Note "password sent"
</send>
  </alias>
</aliases>


Template:pasting
For advice on how to copy the above, and paste it into MUSHclient, please see Pasting XML.


It sends the password (obviously you change it between the quotes (note a single quote followed by a double-quote there)), without colour codes.

So connect to the chat server, and instead of chatting your password type "chatpass" which will invoke this alias, and it will send the password without the colour codes. I tested it with Wireshark, and the codes look exactly the same as what you posted, so the server *should* accept it.
#20
Works like a charm!
Thank you for your time and help! I have yet to receive better tech support for any product I've used than what you gave me here :) Yet another reason to continue using MUSH for all my mudding needs!

Have a great weekend!