| Chat without MXP | Wed Nov 25 22:13:31 2009 MST |
| Not sure if this will be helpful to you, but IOM has chat
monitor support for Portal if you look at help portal. |
| >Chat without MXP | Thu Nov 26 09:16:06 2009 MST |
| On Wed Nov 25 22:13:31 2009 Jomo wrote post #3:
> Not sure if this will be helpful to you, but IOM has chat
> monitor support for Portal if you look at help portal.
Hmm, help portal didn'T tell me anything about how to turn it on...
Either I'm doing something wrong, or things are like this:
For both portal and MXP, the mud expects the client to send them
something first and thus "tell" the mud that it can handle either
of the protocols. I doubt there are ways to turn either feature
on by force, i. e. by a player command. Trying to do so with
mxp party or mxp channel didn't visibly change anything for me
at least. So I'm still stuck for party channel. For everything
else I have at least found ways... Though they may not be very
'beautiful'... |
| >>Chat without MXP | Thu Nov 26 19:36:45 2009 MST |
| stupid question: did you turn mxp on?
i understand, btw, what you're talking about, but frankly i wish
we'd get rid of mxp stuff. i think it gives zmud people an annoying
advantage in certain situations.
well, zmud and any other client (i include cmud with zmud) |
| >Chat without MXP | Fri Nov 27 01:38:05 2009 MST |
| MXP is just messages. You can get the same info w/o it.
Haven't found anything new that i can do with MXP that i couldn't before. |
| >>Chat without MXP | Fri Nov 27 02:26:31 2009 MST |
| On Fri Nov 27 01:38:05 2009 Snoop wrote post #9:
> MXP is just messages. You can get the same info w/o it.
> Haven't found anything new that i can do with MXP that i couldn't before.
09:40:50 You tell Snoop : tell me how it looks like with mxp actvely turned on
09:41:50 Snoop tells you: just sends tags, like you get the party line with
<PARTY_LINE>stuff</PARTY_LINE>
09:42:01 Snoop tells you: tho you don't see the tags in the client ofc
09:42:42 You tell Snoop : OK. How does it look like if 'stuff' is
more than a line?
09:43:36 Snoop tells you: same as anything
09:44:56 You tell Snoop : would you agree that it's most probably
<PARTY_LINE>blah blah
blah{linebreak}bleh bleh bleh</PARTY_LINE>?
09:45:18 You tell Snoop : i mean, even if you can't see it
09:46:24 Snoop tells you: not really =) there isn't any linebreak
sent by the server, so
any linebreak would be client side, and so it should know it's not really
there =)
09:47:06 You tell Snoop : oh, there isn't...
09:47:16 You tell Snoop : dream on
09:47:31 Snoop tells you: haha
09:47:43 Snoop tells you: linebreaks are only there cause you run
out of monitor
09:48:08 You tell Snoop : no, they are sent by the server side
09:48:47 Snoop tells you: only at the end of the message =) not in
the middle of it (as
you implied)
09:49:07 You tell Snoop : a lie with standard settings
09:51:13 You tell Snoop : type columns
09:52:16 Snoop tells you: that's interpreted by the client
09:52:40 You tell Snoop : no, it's not
09:53:35 You tell Snoop : please, stop being a smartass though you
have no clue
regarding this topic
09:53:45 Snoop tells you: haha
09:53:50 Snoop tells you: i speak the truth
09:56:37 You tell Snoop : well, claiming that a mud command is
interpreted by the client
just tells me how much you know about the subject
09:58:14 You tell Snoop : just the simple fact that columns is
documented in the mud's
help files and not in your client's should tell you something
10:03:36 You tell Snoop : so i assume i could “fix“ the one problem
with the party
channel by typing columns 9999 or so
10:04:30 You tell Snoop : but you actually don't wanna know how
descriptions for rooms
look like for me then
10:05:15 You tell Snoop (Idle 6m2s): since, I assume, in contrast
to your client, mine
doesn't word wrap incoming text
So, to get back to the beginning... you know, it'd help a big deal
being able to
determine where that party message ends by having some tag
</PARTY_LINE> at the end.
However, I'd rather have more subtle means, like the indentation in
tell, since I
would definitely have to actually see </PARTY_LINE> tag with my
client, even if I
could by some means manage to actively turn MXP on with it. As you
can see above,
triggering on the indentation works quite fine, since the above is a
(copy-edited)
paste of my communications window (and not from last tell).
I just think, we have this columns command, and party channel and
tell uses it, but
in different ways, while the other channels don't... I don't think
bringing that in
line would be a bad thing, so why not make it all work like tell works...
|
| >>>Chat without MXP | Fri Nov 27 02:30:57 2009 MST |
| OK, I have to admit, in my last posting, the captured output does no
longer look like in my window since it actually got word wrapped by
the mud, lol. |
| >Chat without MXP | Fri Nov 27 04:56:35 2009 MST |
| Guess you'll just have to live in an uncaptured world. |
| >>Chat without MXP | Fri Nov 27 17:31:26 2009 MST |
| On Thu Nov 26 09:16:06 2009 Astarte wrote post #6:
> On Wed Nov 25 22:13:31 2009 Jomo wrote post #3:
> > Not sure if this will be helpful to you, but IOM has chat
> > monitor support for Portal if you look at help portal.
> Hmm, help portal didn'T tell me anything about how to turn it on...
> Either I'm doing something wrong, or things are like this:
> For both portal and MXP, the mud expects the client to send them
> something first and thus "tell" the mud that it can handle either
> of the protocols. I doubt there are ways to turn either feature
> on by force, i. e. by a player command. Trying to do so with
> mxp party or mxp channel didn't visibly change anything for me
> at least. So I'm still stuck for party channel. For everything
> else I have at least found ways... Though they may not be very
> 'beautiful'...
Portal you might have to kick start it. I forget the optino
but its under file.
Last time I looked they were supposed to trigger on something
in our login screen which we had. their triggers was not firing
correctly.
|
| >>>Chat without MXP | Fri Nov 27 17:35:43 2009 MST |
| > tell, since I
> would definitely have to actually see </PARTY_LINE> tag with my
> client, even if I
> could by some means manage to actively turn MXP on with it. As you
> can see above,
> triggering on the indentation works quite fine, since the above is a
> (copy-edited)
> paste of my communications window (and not from last tell).
> I just think, we have this columns command, and party channel and
> tell uses it, but
> in different ways, while the other channels don't... I don't think
> bringing that in
> line would be a bad thing, so why not make it all work like tell works...
>
>
snipped a lot of stuff here.
You are both correct and wrong in certain parts.
The client has the option to tell the mud what its column settings should be.
not all clients support that of course so you can adjust it
manually.
The mud puts the linefeeds in at the setting you specified.
However... when MXP is enabled the linefeeds are not sent otherwise
the closing tag is not found.
|
|
