Zugg Software :: View topic - Automapper trigger and database questions

Beginner Joined: 24 Aug 2008 Posts: 16 Location: NYC

I defined all the #TAG riggers for the automapper but it seems to run incredibly slow and often creates new rooms for irrelevant lines.
Question: in mapper Configureation settings there is a [Map Script] and [Zone Script]. Was I supposed to create triggers there?

I managed to setup the mapper to work without #TAG triggers with the side effect that it records objects in the room as Description.
Question: since the map is stored in a relational database, do I have manual access to

Posted: Wed Aug 27, 2008 8:16 pm

Hmmm...

Well without seeing your code, we can't really make many recommendations. But unless there are some poorly defined triggers, it shouldn't be running that much different.

As for updating the DB directly, it's technically possible but I don't recommend it. The table structure isn't formally documented, although a search of the forums should turn it up. With the mapper re-write that's going on you may not have a long term solution. Most importantly, you're not really address the true problem of proper room captures.

Beginner Joined: 24 Aug 2008 Posts: 16 Location: NYC

Triggers are described in my last post [url]http://forums.zuggsoft.com/forums/viewtopic.php?t=31612 [/url]
I since modified and tried to disable/enable some of them. I also watched debug console and all triggers are firing properly as intended.
What I think is happening is that the Automapper tries to use some of it's own built-in "intelligence" in parallel which leads to very complex computations (as long as a minute to map one room) and some odd behavior.
I am wondering if I was supposed to define the triggers in the [Map Script] area, and if not then what purpose does the [map script] serve?

Posted: Wed Aug 27, 2008 11:49 pm

No, do *not* put #TAG triggers into the Map Script area. That is for advanced map scripting, so you should ignore it.

If you want to edit the room description that is captured by the mapper, click the Room Properties button in the mapper toolbar when in Map Mode and then you can edit the name, description, and other properties.

But the best way is to create #NOMAP triggers to ignore the lines from the MUD that you don't want it to capture.

Also remember that after every change to your #TAG triggers, you need to rerun the Config/Reconfig menu command in the mapper.