Unknown2007-10-05 14:34:15
In many Lusternian help files, syntax is displayed using less than and greater than signs for generic parameters, such as:
INR
or
NATURE CURSE
Well, in MUSHClient, it accepts MXP from Lusternia, and it interprets these things as HTML tags, and they don't render. So, when I look at a help file that displays syntax, the same lines would look like this:
INR
NATURE CURSE
Now, most of the time, I can figure it out. However, the inability to see the full syntax for commands has led to some degree of frustration for me for more complicated commands or commands I rarely use, and I've taken to using the website to look up most things. Even so, not everything I need to see is available in a public help file.
I could turn off MXP for Lusternia, but then my mapper (IMap via MudBot) doesn't display properly.
Is there something I can do in MUSHClient that would display those tags without completely disabling MXP?
INR
or
NATURE CURSE
Well, in MUSHClient, it accepts MXP from Lusternia, and it interprets these things as HTML tags, and they don't render. So, when I look at a help file that displays syntax, the same lines would look like this:
INR
NATURE CURSE
Now, most of the time, I can figure it out. However, the inability to see the full syntax for commands has led to some degree of frustration for me for more complicated commands or commands I rarely use, and I've taken to using the website to look up most things. Even so, not everything I need to see is available in a public help file.
I could turn off MXP for Lusternia, but then my mapper (IMap via MudBot) doesn't display properly.
Is there something I can do in MUSHClient that would display those tags without completely disabling MXP?
Unknown2007-10-05 15:55:03
I turned off my IMap MXP option because of this problem. No real easy way around it, I'm afraid. It's a bug in IMap, I'm pretty sure.
Okin2007-10-06 02:17:08
How do you do whatever you just said?
Unknown2007-10-06 11:43:00
map config map_mxp off
You may also need to turn off exits_mxp and title_mxp.
You may also need to turn off exits_mxp and title_mxp.
Unknown2007-10-06 14:28:36
QUOTE(Zarquan @ Oct 6 2007, 06:43 AM) 447150
map config map_mxp off
You may also need to turn off exits_mxp and title_mxp.
You may also need to turn off exits_mxp and title_mxp.
Will doing this in config.mapper do the same thing?
Disable-MXPTitle yes
Disable-MXPExits yes
Disable-MXPMap yes
Unknown2007-10-06 15:17:27
Yes. That's what those commands modify, so doing it directly and then loading your map will work just the same.
Unknown2007-10-06 15:29:24
QUOTE(Zarquan @ Oct 6 2007, 10:17 AM) 447180
Yes. That's what those commands modify, so doing it directly and then loading your map will work just the same.
Thanks! I haven't had time to test it, yet, but this has been bothering me a long time.
Will I need to disable MXP on the MUSHClient side, too?
Unknown2007-10-06 18:50:39
If MUSHclient handles the MXP stuff correctly (and I think it does), you won't have to disable it in the client.
Okin2007-10-07 00:38:22
I tried doing those three things and it still didn't show .
Unknown2007-10-11 20:26:12
QUOTE(Okin @ Oct 6 2007, 07:38 PM) 447292
I tried doing those three things and it still didn't show .
I had to disable MXP in MUSHClient as well. Once I had those settings changed in the mapper file and told my MUSHClient settings for Lusternia never to use MXP, the whole thing worked like a charm.
Okin2007-10-12 02:54:19
How does that affect the mapper?
Unknown2007-10-12 04:23:46
QUOTE(Okin @ Oct 11 2007, 09:54 PM) 449037
How does that affect the mapper?
Well, if I disabled MXP in Mush, but not the Mapper, the tag thing worked, but my mapper was all screwy.
If I disabled MXP in the mapper (per Z's intructions), but not in Mush, nothing seemed to happen.
But if I disable it in both, everything works fine.