Mudlet - Forum

I've noticed older maps can act funky. One instance is with special exits, an older map of mine seems to lack the room lock status. I thought the version control system in the restore/serialization would fix this upon saving of a map, but it doesn't seem to cover all the cases. Users who visit older profiles might get unexpected behavior from out of date maps. Has anyone else had similar issues with older maps on newer mudlet releases (aka my repo) where such a tool might be worthwhile?

Older maps just didn't load for me, I had to re-download map mine - which won't be feasible for those who did their mapping. I'd say a tool would be definitely worthwhile.

the exit lock was because adding special exits by default doesn't set the lock status, hence the funkyness. I defaulted it to unlocked exits in my repo. What map wasn't working for you

Well try connecting to a default achaea.com profile on the latest published binary (not sf git, since it's been merged with your stuff), opening the mapper on it - it'll download a map, and then opening that map on current git. That doesn't seem to work.

I installed test4 for windows and my custom map doesn't work at all, I can't find it in the slightest. None of the functions will bring it up, even trying to manually do centerview(1337) for example, returns nothing.

Not sure what to do

Send me the latest version of your map by email (-> Mudlet about dialog for details).

This is due to a bug in test4. I've uploaded test4b to fix this issue. https://sourceforge.net/projects/mudlet/files/

4b still seems to have issues related to specialExits

specifically, the function AddSpecialExit. it cuts 1 character off the command

so AddSpecialExit(2,3"portal") ends up creating an exit "ortal". I checked out the code on repository and it looks like the issue TRooms.cpp on 299 (i'm pretty sure the cmd is supposed to be _cmd). I gamed the code a bit and realized if I did AddSpecialExit(2,3,"1portal") it would work.

I'm not sure if it's a side effect but getSpecialExits now returns {id, {command,'0}} instead of what's in the documentation of {id, command}

This behavior is also inconsistent with getSpecialExitsSwap which DOES return {command, id}... however, the command still have the 0 prepended to it

There's also related issues to getSpecialExits and getSpecialExitsSwap. Here's some sample output from test4b

In the topic with test4b I posted a fix for the exits. Also, getspecialexits is different because that's the version I changed to return the exit and lock status as tables