Zugg Software :: View topic

Apprentice Joined: 08 Dec 2005 Posts: 108

I can't seem to be able to see any of the telnet 102 triggers from aardwolf. Bellow is my code that I am using to see the triggers. Has any one been able to get the telnet triggers to work for aardwolf? If so how did you do that?

Posted: Mon Nov 17, 2008 2:09 pm

Sometime displaying things like this won't work because telnet suboption text comes in the middle of lines. What you should do is open the script debugger, making sure you have i (raw input/output) messages turned on, and then connect.

You should see the server and client communicating, the server saying IAC WILL 102 and CMUD replying IAC DO 102 - this means that both the client and server have reported that they're able to send and receive data on suboption 102. Then you'll be able to see in the debugger whenever something comes in or goes out over the suboption.

In looks like 0.4031 | i MudName <<IAC><SB><102>Text to trigger on here<LF> and out looks like i MudName ><IAC><SB><102>text sent to MUD here<LF>. You send text over suboptions using the #sendsb command.

Apprentice Joined: 08 Dec 2005 Posts: 108

Thanks for the heads up on the debuger. I worked with Charneous last night, and we weren't able to get anywhere on my end. I am able to see the initial <102><do> and <102><will> at the beggining of the session. But after that I am not able to see any more come in to my session using the debugger. Just to make sure that might settings weren't fubared. I tried sending a <102> to the mud and that worked just fine.
Thanks in advance.

Posted: Mon Nov 17, 2008 4:50 pm

Yeah. I spent quite a bit of time with him, checking his CMUD setup compared to mine. Everything matched perfectly. Had him run the script debugger, set the same messages as mine, ran some tests, not once did he see the telopts prompts.

He did do a reinstall, but one thing I didn't suggest is any .ini files associated with CMUD that might cause them to not appear on the screen. Either way, it's very weird for it not to show up on his when it shows up on mine with the same settings.

Charneus

Apprentice Joined: 18 Feb 2007 Posts: 190

cmud does not ack 102 chan on its own, try manually sending iac do 102
sendraw("\255\253\102\r")

Posted: Mon Nov 17, 2008 5:46 pm

If you have a trigger assigned to telnet option 102, then CMUD *should* send the IAC DO. And Cazador mentioned that he is seeing the DO and WILL at the beginning of the session.

Isn't there a command on Aardwolf that you need to enter to enable all of this <102> stuff? It sounds like it's working differently for Charneus and Cazador even though they are using the same settings, so that's what made me think about whether there is a command on the MUD that needs to be used to activate this feature.

Posted: Mon Nov 17, 2008 6:28 pm

Right. I should have mentioned that I did make sure he had the telopts command enabled, so that wasn't the problem. He even created another character, enabled the telopts, still nothing.

Charneus

Posted: Mon Nov 17, 2008 7:53 pm

Have you tried creating a new session on your computer with a stripped-down version of your Telnet triggers? Once you have it working on your system in a small test package then you can send him your exact PKG file and see what happens on his system. I suppose you could even send your CMUD.INI file with the global preferences to see if there is some difference there.

If you can pin it down to a problem in CMUD then I can add it to the bug list, but for now I'm as clueless as everyone else as to why it works for you and not him.

Apprentice Joined: 18 Feb 2007 Posts: 190

nopers, it sends iac will not iac do, and aard likes it to be iac do from client to send over 102
you have to manually send iac do Cool

btw, telopts has _nothing_ to do with it

Posted: Mon Nov 17, 2008 11:05 pm

You're right actually, CMUD is sending IAC WILL 102, but this is correct. Technically either party can send either WILL or DO and that's correct - most of the time servers send DO and clients send WILL, though. Aard should fix this. From RFC 855:

Posted: Mon Nov 17, 2008 11:54 pm

Yes, you should tell Aardwolf about this. It is very common for MUD servers to get this wrong. If the MUD sends an IAC WILL, then the client is supposed to send IAC DO. If the MUD sends IAC DO then the client responds with IAC WILL.

So check to see what Aardwolf is sending. If they are sending IAC DO, then CMUD is responding correctly and they should fix their server to respond to IAC WILL from the client. (You can see what the MUD is sending with the Raw Input message in the Script debugger)

But I still don't think this has anything to do with the problem since Charneus has said that it's working fine for him.

Apprentice Joined: 08 Dec 2005 Posts: 108

Apprentice Joined: 08 Dec 2005 Posts: 108

My telnet negotiation sequence

i Aardwolf ><IAC><DO><86>
i Aardwolf <<IAC><SB><86><IAC><SE>
i Aardwolf *<IAC><WILL><86><IAC><WILL><85><IAC><DO><102><IAC><DONT><103><IAC><WILL><102>#############################################################################<LF><CR>
##[ --- Welcome to Aardwolf MUD --- ]##########################<LF><CR>
##[ ]############ /" #########<LF><CR>
.
.
.
################# / ; #################<LF><CR>
############### / ; ##################<LF><CR>
-----------------------------------------------------------------------------<LF><CR>
What be thy name, adventurer?
i Aardwolf ><IAC><DONT><85>
i Aardwolf ><IAC><WILL><102>

Apprentice Joined: 08 Dec 2005 Posts: 108

I worked some more with Charneus, It looks like this is is a mud issue. He was able to get it to work with his character w/ my settings. then he tried a creating a new char, and it didn't work at that point. Thanks everyone for your help

Apprentice Joined: 18 Feb 2007 Posts: 190

run above from lua comm line mate, wo # Razz

with zscript cmd youd need something like #sendraw %char(255)%char(253)%char(102)%char(13)

aardwolf should be doing lots of things differently, starting with not tailoring build in features for poorly written scripts shipped with its 'customized' client and either expanding telnet on whole front or moving to standardized mxp stead custom tags, unfortunately lasher has too many clappers around and voices of reason tend to get ignored.

Posted: Tue Nov 18, 2008 6:04 pm

The #sendraw command does not recognize the \nnn syntax. intoK is correct that using the %char function in CMUD is correct. But you don't need the %char(13) at the end. Telnet option sequences do not need to be terminated by any newline.

Cazador: It looks like you stopped the debug output too soon. I see that Aardwolf is sending both IAC DO 102 and IAC WILL 102 and then sending IAC WILL 102 *again* at your name prompt. But I don't see the following text that shows what CMUD is sending back in return.

Also, it looks like it might be a problem with their MCCP compression implementation. The package that has the Welcome to Aardwolf data is compressed (indicated by the * at the beginning of the line). But the IAC DONT 85 and IAC WILL 102 at the end are not compressed. So try turning off MCCP compression in your CMUD Preferences to see if that makes any difference.

Just so you can understand the Script Debugger output for the "i" message (raw input/output), the first character can be a > or < or * character. The < character indicates a normal package received from the MUD. The > character indicates a packet send TO the MUD by CMUD, and a * indicates a compressed packet received from the MUD.

If we can pin this down to something specific Aardwolf is doing wrong, then I can contact Lasher myself and point him to this thread. I'm sure he wants to make sure this all works on zMUD and CMUD.

Apprentice Joined: 08 Dec 2005 Posts: 108

I turned mccp off, and no luck. A longer version of the log is bellow. I Also tried doing what intoK suggested, and had no luck doing that.

Posted: Tue Nov 18, 2008 7:54 pm

OK, sorry I made a mistake in my < vs > comment. I have fixed my post above. The < means a line received FROM the MUD, and the > is a line sent TO the MUD.

So again, it looks like CMUD is sending the IAC WILL 102 in response to the MUD sending IAC DO 102. Once this has been done, CMUD is ignoring the IAC WILL 102 from the MUD because CMUD knows that it has already negotiated that telnet option and it is trying to avoid infinite-loop telnet negotiation.

I will contact Lasher about this. Aardwolf should NOT be sending both IAC DO 102 and IAC WILL 102. It needs to pick one or the other. Otherwise they are just going to have more problems with other telnet and MUD clients.

I still don't understand why it works for an existing character but not for a new character on Aardwolf. Makes me think that something has changed recently on the MUD or something. Right now I'm in the middle of the mapper coding, so I haven't had time to look into this myself. But I'll try to test it on my own Aardwolf character.

Apprentice Joined: 18 Feb 2007 Posts: 190

strange, just tested with my alt and new char, both on empty sessions and #sendraw %char(255)%char(253)%char(102) enabled them just fine in both cases

do some debugger logging from pasting that and doing sit stand after?

Apprentice Joined: 08 Dec 2005 Posts: 108

Now this is odd.
intoK suggestion worked this time for me. After I logged in w/ my character I did the #sendraw command
I started getting things like
i Aardwolf <<IAC><SB><102>e<1><IAC><SE>
i Aardwolf <<IAC><SB><102>e<1><IAC><SE>

So the next question is how do I get it to trigger on a specific return sequence.
bellow are the supported codes

100,1 At login screen, no player yet
100,2 Player at MOTD or other login sequence
100,3 Player fully active and able to receive MUD commands
100,4 Player AFK
100,5 Player in note mode
100,6 Player in Building/Edit mode
100,7 Player at paged output prompt

Posted: Tue Nov 18, 2008 10:48 pm

Right. It works because the code that intoK gave was for IAC DO 102, whereas CMUD is normally sending IAC WILL 102. I have emailed Lasher, so hopefully he can look into this.

For now, just do the #SENDRAW from within your Telnet 102 trigger. Set the "Prompt" option and that will cause the trigger to only fire during the telnet option negotiation.

In other words, when the MUD sends a DO/WILL, CMUD will send a WILL/DO and will call your trigger with the Prompt option (like a Prompt trigger). Then, when CMUD receives the IAC SB 102 suboption data, it will call your Telnet 102 trigger with the "Newline" option set.

The data sent by the MUD between the IAC SB 102 and the IAC SE is used as the trigger pattern for your option 102 trigger. So you'll need details on exactly what data the MUD is sending for you to create a trigger pattern that fires on that data.

Apprentice Joined: 08 Dec 2005 Posts: 108

I made the following trigger to catch the WILL, but it isn't catching did i get my pattern incorrect?

Posted: Wed Nov 19, 2008 4:05 am

Firstly, there won't be a %1 in this script - I'm not sure what you're trying to do there. Secondly, you shouldn't have spaces in your setting names. Thirdly, you shouldn't need a pattern for the trigger.

Posted: Wed Nov 19, 2008 4:28 pm

If you set the prompt="true" option, then you don't need any pattern at all. The data is only sent to the trigger when receiving an IAC SB 102 from the MUD. When receiving a IAC WILL, your Prompt trigger is called without any pattern. So just leave the pattern blank.

Oh yeah, so "what Fang said". ;)

Apprentice Joined: 08 Dec 2005 Posts: 108

I had tried that, but the trigger kept fireing on all the IAC SB 102 commands comming from the mud, not just the WILL. At least for now I just added it to my onconnect event, and waited 10 ms. That seemed to work just fine for me.