Zugg Software :: View topic

Newbie Joined: 01 Oct 2008 Posts: 2

I've recently switched to cMUD (version 2.36) from zMUD, and have begun to experience some problems with chat channels in PennMUSH (version 1.7.7). I have my Word Wrap on, set to 83 characters. When a multi-line communication comes in over the comsys, it will display fine. Then, when someone else says something over the same channel, I will lose everything after the first line from the first communication. Example:

At first:
<Public> Someone says, "Blah blah, this is going to be an example of a multi-line
comsys communication.

Then someone else says something and we get this:
<Public> Someone says, "Blah blah, this is going to be an example of a multi-line
<Public> Someone Else says, "Something else here."

Any ideas about what is causing this, and a fix? Thanks!

Posted: Wed Oct 01, 2008 8:03 pm

Sounds to me like your multiline makes use of #GAGON.
Either you need to make it smarter in telling single lines from multilines... or you need a better cleanup to do #GAGOFF

Posted: Thu Oct 02, 2008 4:21 pm

We would need to see your scripts that are running. You can turn on the Script Debugger in the Window menu to see what triggers are running that might be gagging the text.

Also, make sure you are using client-side word wrapping. Turn off any line length setting in the MUD and then use the word wrap setting in CMUD. It sounds like you are already doing that, but I wanted to make sure you were not using some word wrap feature on PennMUSH.

Also remember that by default, CMUD (and also zMUD) will gag any line that contains your password. So be sure your MUD password isn't set to something simple that the MUD might display.

Newbie Joined: 01 Oct 2008 Posts: 2

I'm not running any scripts at all, to my knowledge. If I am, I have no idea where they came from or how they were turned on!

I am using client-side wrapping only. As far as I am aware, there is no way to set a line length in the game. It isn't my password that is being gagged, it's letters and numbers, and not something simple that someone might accidentally say.

I turned on the Script Debugger, and waited patiently for it to happen again. For a while, things were okay; multi-line chat messages were getting through, but now it's started burping again. Here's what the Debugger caught:

| a Dinah @ ]<Public> Callisto says, "Just a friendly wave, Merry. No ulterior motives this time. B-)"
0.1680 | a Dinah @ |<Public> Callisto says, "Just a friendly wave, Merry. No ulterior motives this
34.031 | a Dinah @ ] Oliver Queen says, "-This- time..."
0.1792 | a Dinah @ |<Public> Oliver Queen says, "-This- time..."

Here's what I saw:

<Public> Callisto says, "Just a friendly wave, Merry. No ulterior motives this
<Public> Oliver Queen says, "-This- time..."

Also, I don't know about #GAGON, or how that would have gotten turned on. I have typed #GAGOFF but it didn't help.

Sorcerer Joined: 13 Jan 2006 Posts: 715

I'm curious if this could be something improperly implemented server side in the way it sends the communications having unexpected consequences? I doubt it, but it'd be interesting if it was.

Posted: Sat Oct 04, 2008 8:15 am

It could be - CMUD has different categories for the messages it shows in the script debugger. I assume you already had f messages on when you did the above test - try turning on h and i messages as well and showing us exactly what the MUD's sent (ANSI codes and all) during that time. Could be they're doing something weird moving the cursor around.

Sorcerer Joined: 13 Jan 2006 Posts: 715

This is true Fang, but I thought MUD developers these days would be smart enough to leave the majority of that client side heh ;)

Of course, there is always some newbie coder who thinks *his* way is the right way.

Posted: Sat Oct 04, 2008 4:59 pm

I wonder if it's because of the "<Public>" part of the line that was missed. Maybe MXP is getting confused somehow and it thinks this is an MXP/HTML tag. Go into your MXP Preferences and make sure the "Show unknown tags" is turned on to see if that helps. You can also try turning off MXP completely just to see if that fixes the problem with the displayed text.