Zugg Software :: View topic

Novice Joined: 09 Oct 2007 Posts: 36

Hey all again.
In the mud i'm playing, it has a 'map' an in game that allows you to preview the rooms around you.
Its a very nice feature to have but it spams you a lot, so the best solution has always been to Capture it
here is what i get from the mud

Posted: Fri Mar 28, 2008 7:52 pm

Your best bet is to but your original triggers into a local module. Then add that module to your main window, and make sure it's disabled in your capture window.

In summary it's a scoping thing, and by doing it that way you basically tell CMUD to only match the text for the main window. Sorry for the crappy explanation, but I'm sick. Embarassed

Novice Joined: 09 Oct 2007 Posts: 36

That does make sense, but how do i "make sure it's disabled in your capture window. "
Thanks.

Posted: Sat Mar 29, 2008 10:05 am

Are the triggers for your mapper in a module, or a window? You should put them in the window you want them to apply to (so not the capture window) rather than in a global module - they'll fire in the capture window if they're in a global module.

Novice Joined: 09 Oct 2007 Posts: 36

Ahh, I've put almost all of my scripts in Module form. :(

Posted: Sat Mar 29, 2008 11:07 am

You have a couple of options - either put the scripts you only want firing in one window in that window, or put the capture window in a separate package from the module and the main window and have the module local, or put the main window in a separate package to the capture window and the module and set it to external.

Novice Joined: 09 Oct 2007 Posts: 36

is the #C+ not inteneded for use as i am using it?
or is there another reason for the lag it causes?

Wizard Joined: 11 Jul 2002 Posts: 1265 Location: USA

You aren't seeing that Fang has already answered those questions so I will try again.

Look at this structure.

Novice Joined: 09 Oct 2007 Posts: 36

No, I do see that he did answer this.
I was wondering if the lag on #C was intended, or if i was using it for an undesired use.
I've already done what fang said and it works.
but thanks for your in depth answer.

Novice Joined: 09 Oct 2007 Posts: 36

Well It appears that the map capture script does not work as intended still
Its still very laggy, enough that i have to disable it, Hopefully soon I can figure this out.. but the #cap when triggering on (*) seems to be EXTREMELY laggy
Possible bug.. Might be worth looking into.

Posted: Mon Mar 31, 2008 12:49 am

I think that may the result of the trigger your using. As has been discussed in other forum topics, (*) is a greedy pattern matcher and takes some time to evaluate. You can try detecting the last line, (if it always eight lines) then doing #CAPTURE 8 MapWindow, which should the last 8 lines to the MUD window. that should speed things up a bit. it might also help if no other (or at least as few as possible) are trying to match when you receive this info. If you do a search on speed in CMUD you'll find a topic already discussing the nuances of this.

I hope that helps.

Novice Joined: 09 Oct 2007 Posts: 36

Just for reference.. I did what you suggested Tech
I did #Capture 17 MapCapture on the Mapend line
I also did #gag -17 on it too
Its quick and works fine, Thanks for all help