Zugg Software :: View topic

Posted: Thu Apr 23, 2009 7:14 pm

Any chance that when the mapper is configured it will make and show us the #TAG triggers it uses to allow us to easily edit them?

Having the configuration as easily editable settings will allow people to package up and share maps easier. Once we can distribute them via the package library.

Posted: Thu Apr 23, 2009 8:37 pm

Afaik the mapper doesn't actually create #tag triggers, it does some jiggery pokery with paragraphs and who knows what else. The #tag triggers are a way of telling the configuration where to weave its sorcery to aid that system, they don't supersede it.

Posted: Thu Apr 23, 2009 9:02 pm

Yes... this was an idea to change that into the standard settings, for ease of use/sharing.

The old system rarely works (for me) without the use of #TAG triggers at all, so why not make it the norm and do away with the old format?

Posted: Thu Apr 23, 2009 9:23 pm

Well, yes, that's perhaps something that's going to be examined in future phases of the mapper rewrite. I remember Zugg mentioning configuration as one of the things he wanted to examine, but I don't know what kind of priority that is.

But you said "the #tag triggers it uses", and I just wanted to make it clear that using the configuration wizard at the moment doesn't involve any kind of triggers, so there's nothing to show. The mapper configuration can usually be bullied into working for any MUD, but it takes a lot of manipulation of numbers that you're not really sure exactly what they do. Using #tag is normally simpler. So there's definitely room for improvement there :P

Posted: Thu Apr 23, 2009 9:29 pm

Yes.. but I also mentioned it making them first :p

I was already clear on how it currently works.

Just offering ideas for the configuration rewrite.

Posted: Thu Apr 23, 2009 9:41 pm

It would be ideal if new users could download an expertly configured map tag package for their mud. Many frustrations seem to arise from configuring the mapper.

Posted: Fri Apr 24, 2009 7:30 pm

The Phase 2 of the new mapper will deal with the mapper configuration. However, the existing AI algorithms for the mapper will remain as the default. The #TAG command is a way to override the mapper AI and will be improved to work more reliably. The existing AI algorithms work on many MUDs and I'm not going to remove it just because it doesn't work on your specific MUD.

There is no way to simulate the current mapper AI with simple #TAG triggers, so as mentioned above, there isn't anything to be shown.

The main focus of Phase 2 will be improving the #TAG commands to work better, add a feature to the Room Properties to allow you to see the #TAG trigger results for debugging, and most importantly, to allow map configurations to be stored in the Shared Package Library so you can more easily get an existing configuration that works with your specific MUD.

Posted: Fri Apr 24, 2009 7:54 pm

Cool, can't wait to get my hands on it.

In this phase will you also be attacking some of the long standing bugs associated with the mapper?

Posted: Mon Apr 27, 2009 5:10 pm

Posted: Mon Apr 27, 2009 6:11 pm

Here are a few of the items I've posted on over the last year:

[3.05] Mapper Issues with %inwalk %walkactive %destroom and onWalkEnd
http://forums.zuggsoft.com/forums/viewtopic.php?t=33205

[3.03a] #NODIR incorrectly clearing more than current dir in the walk queue
http://forums.zuggsoft.com/forums/viewtopic.php?t=32608

[3.03a] Directions Editing and longstanding directions work-around
http://forums.zuggsoft.com/forums/viewtopic.php?t=32505

[2.21] Mapper issues with non-standard exits
http://forums.zuggsoft.com/forums/viewtopic.php?t=30306

[2.18] Slowdown of 0.4s in walking when I enable "Match Room Name" in Map Pref
http://forums.zuggsoft.com/forums/viewtopic.php?t=29504