Zugg Software :: View topic - [3.27]Mapper problems, probably due to new feature

Posted: Sat Sep 18, 2010 5:26 pm

For whatever reason, my mapper is automatically switching zones to a non-selected one and creating new rooms there. I tried #ZONE "areaname" to set it to the proper zone name, but it's failed. It's getting irritating quickly to try to map with this going on.

I don't even know how or why it's doing it, either... but I'm guessing it's with the 'new rooms will only be created in the current zone selected'.

Charneus

Posted: Sat Sep 18, 2010 5:41 pm

Yes, that would be the bug fix that would be causing the problem. Using the #ZONE command *should* fix it, or even just selecting the proper zone from the drop-down list. Do you have any scripts using %room or %zone functions that might be switching zones in the background? I'll play with Aardwolf a bit to see if I can reproduce this since it's a fairly serious issue. It's something I worried about when I added the #ZONE command and fixed this issue, but I didn't find any problems in my limited testing with it. Guess I need to look some more, but any additional info on this would be helpful.

Posted: Sat Sep 18, 2010 6:04 pm

Currently, I have the following trigger:

Wizard Joined: 17 Jun 2006 Posts: 1201

This is happening to me too. If I use the menu and move a room to another zone from the list or to a new zone and then walk so it creates the next room, it suddenly switches back to the old zone creates a room there. Then when I walk again to create the next room, it switches back to the other zone and creates a room. Then on the next room it switches back to the old zone. It just keeps doing this. Every other room it creates the room in the other zone and goes back and forth.

Apprentice Joined: 03 Feb 2007 Posts: 170

Doing it to me as well, quite annoying.

EDIT: Worth noting I have abslutely zero scripts that use %room or %zone.

Newbie Joined: 31 Jul 2008 Posts: 9

I have the exact same problem described above (particularly oldguy2's description). The only triggers I have that influence the map in any way send #OK or #NOMAP.

Posted: Sun Sep 19, 2010 6:42 pm

This is happening to me as well. It should have made a room in the current zone connected to the room I was coming from, instead it placed it in a random zone. However, it was more serious than this as the room wasn't visible by any means. Teleporting to the room didn't allow me to see it, it simply took me to that zone with nothing selected. So it ended up orphaning the room it created as there was no way for me to select it or even to see it to operate upon it to correct it.

Apprentice Joined: 03 Feb 2007 Posts: 170

3.28 likely to be releases soon? Otherwise likely going to try and find 3.26 somewhere on the web to revert back to it till 3.28 is released as this is somewhat of a gamebreaker.

Posted: Mon Sep 20, 2010 5:23 pm

Yes, I should have an update out later today or tomorrow, depending upon other bug reports.

Wizard Joined: 17 Jun 2006 Posts: 1201

Posted: Mon Sep 20, 2010 6:14 pm

I'll give that a try. I was thinking I'd need to dust off my perl mapper cleanup script to find and delete them, but this is a much less drastic fix. Thanks!