Register to post in forums, or Log in to your existing account
 

Play RetroMUD
Post new topic  Reply to topic     Home » Forums » CMUD Beta Forum
sabman
Novice


Joined: 17 Aug 2007
Posts: 34

PostPosted: Mon Aug 27, 2007 11:59 pm   

Question for Imperian players with CMUD 2.1 and IMTS
 
I've noticed that MXP doesn't seem to be working for me in CMud 2.1. Switiching to zmud it works perfeclty; I can MAP 1 and click on the springs and it builds a path there. I don't seem to be able to do that with 2.1, and before I submitted a bug, I wanted to ask if anyone else is noticing that, in case it's a user error.
Reply with quote
Zugg
MASTER


Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA

PostPosted: Wed Aug 29, 2007 7:50 pm   
 
I have moved this topic to the CMUD Beta Forum. Please try to keep all topics relating to the 2.01 beta in the BETA forum and not the general forum.

I don't know what "IMTS" is. For MUD specific questions, please post as much information as possible so that people who don't play the specific MUD can still try to help. Perhaps you can post an example of what zMUD is doing compared to what CMUD sends to the MUD.
Reply with quote
Caled
Sorcerer


Joined: 21 Oct 2000
Posts: 821
Location: Australia

PostPosted: Wed Aug 29, 2007 10:24 pm   
 
Sabman is referring to one of the modules that forms a popular proxy program people that play Imperian (also Aetolia and possibly other IRE muds) like to connect through with their normal client. Its known as Mudbot and commonly Whyte's Mapper. IMTS is one of the Mudbot modules that is not actually the mapper (it stands for 'Imperian Modularised Trigger System').

Judging from the question though, Sabman, you're not actually talking about IMTS, but IMapper instead, which makes a lot of sense since if you used IMTS why would you bother with CMUD at all?

The function in particular you seem to be referring to is:


Code:
[b]map[/b]

/--Spinesreach.--------------------------------v5259--\
 \   /     |     \                     |             
 -[ ] [ ]-[ ]-[ ] [ ]-[ ]         [ ]-[^]- - -[ ]- - 
   |       |       |                           |     
 -[ ]     [ ]     [ ]-[ ]                      |     
     \     |     /                             |     
       \   |   /                              [ ]     
         \ | /                                 |     
          [ ]     [o]             [ ]          |     
           |                     /             |     
          [ ] [ ]-[o]     [*] [ ]-[ ] [ ]     [ ]- - 
             \     |         \ | \   /   \ | /       
               \   |          [ ]-[ ]- - -[ ]- - -[^]-
                 \ |     /       /       / | \       
              [ ] [ ]-[ ]      /       /      [ ]     
           |   | /       \   /                       
          [ ]-[ ]    -[ ]-[ ]      /                 
           |                   | /                   
           |                  [ ]                     
                             /                       
\--Time: 180 usec-------------------------------------/
H:3460|3934 [eb] [] 0|0 08:15:13:390[b]map path 5357[/b]

[Path calculated in: 109831 microseconds.]
[Path: se, e, e.]
H:3460|3934 [eb] [] 0|0 08:15:17:234


The first bolded command sent was from the command line, and only went to IMapper. It generates the ansi local map, with MXP output optional. The asterisk indicates where my character is. The rooms are colour coded for room type, and clicking on a room sends "map path <vnum>" to IMapper, which generates the path. Typing "go" will autowalk me to that room.


I have not had time to install 2.01 yet, but Sabman is saying that clicking on the rooms no longer sends the command "map path <vnum>". I won't have time to test this myself until monday, which will be too late for 2.02 - but if someone else could check it out that would be fantastic ;-). It may be a bug with MXP, specifically the hyperlink tags... or something.

Or it might not be a bug at all and could just be Sabman haha.
_________________
Athlon 64 3200+
Win XP Pro x64
Reply with quote
sabman
Novice


Joined: 17 Aug 2007
Posts: 34

PostPosted: Thu Aug 30, 2007 9:59 pm   
 
Sorry, I didn't want to bug it until I knew it was an actual bug, and I think I know the problem.

Someone else submitted a bug where <color stuff> isn't working.

I'm wondering if it's just that MXP isn't working?.

--EDIT

Yes, it seems like there's a bunch of different MXP bugs going on. This is just one way it's coming out.
Reply with quote
Display posts from previous:   
Post new topic   Reply to topic     Home » Forums » CMUD Beta Forum All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

© 2009 Zugg Software. Hosted by Wolfpaw.net