Zugg Software :: View topic - [316Bb

Posted: Mon May 17, 2010 11:22 pm

I am posting this since there was misunderstanding to my added post to a previous problem because it was labeled 316b.
As Charneus pointed out in the last reply to that post, ATCP interferes with the mapper. Which was the original purpose of that post, and the reason I bumped it. Whatever ATCP does prevents the mapper from mapping Aardwolf and the point I was trying to make was that ATCP should not be on by default since it is obvious that it doesn't work for all MUDs.
All the mapping problems which were indicated in that post were resolved by turning ATCP off. The attempt by CMUD of storing the .zfg file in program files (x86) was resolved by updating to 317B, which I had done prior to bumping said post. So currently I have no problems with the mapper, as long as I keep ATCP turned off.

Posted: Tue May 18, 2010 5:14 pm

Do you have any other mapper scripts running (#TAG commands)? Since Aardwolf added ATCP, you shouldn't need your own #TAG commands anymore and it might be interfering with their ATCP stuff. But since I actually play Aardwolf now and then I'll take a look at this after TeSSH is released to see what's going on.

I also know that they will probably be converting their ATCP stuff to the newer GMCP (ATCP2) protocol developed on mudstandards.org to follow what IRE does with it. But the concept of it will be the same as ATCP so if there is a problem with ATCP and the mapper then I still need to fix it.

But ATCP mapping works fine on Achaea, so I'm not sure why it wouldn't work on Aardwolf unless they did something wrong with the implementation.

In any case, you might try a fresh session for Aardwolf with ATCP enabled and create a new map and run the Autoconfig wizard and see if it works out-of-the-box on a clean install to determine if the problem is with your other scripts.