This forum is a read-only archive of the Gammon Software forum (2000–2026). No new posts can be made. Search the archive.

Mapper speedwalk error when current and expected rooms match

Posted by Victorious on Tue 01 Aug 2017 05:01 PM — 5 posts, 21,424 views.

Victorious #0
Hi,

I'm encountering a perplexing error when implementing a mapper modified from the realms of magic mapper example plugin.

When I type mapper goto <room num> to go to a room, it reports an error when reaching the destination. The following is some debug output.

What additional info can I provide that would be useful to try figuring this out? The most notable change I remember making is that exits are built lazily - it doesn't yet capture the exits line, but creates exits (and their inversses) as you move.


wanted 50859
Walking to: Approaching a vine covered temple
A vine covered temple
Location changed to room  14599   A vine covered temple
Fixing up exits
Moved from 14584 to 14599 in direction s
Current destination =  14599
Current return      =  14584
Fixed exit s from room 14584 to be to 14599

Approaching a vine covered temple
Location changed to room  50859   Approaching a vine covered temple
Loading room 50859 from database
Fixing up exits
Moved from 14599 to 50859 in direction s
Current destination =  50859
Current return      =  14599
Fixed exit s from room 14599 to be to 50859
Speedwalk failed! Expected to be in '50859' but ended up in '50859'.
Victorious #1
Just saw an instance of this happening while it is still on the way, and hasn't reached the destination.


Walking to: In the center of the Fire Tower, fifth floor
In the center of the Fire Tower, fourth floor
Location changed to room  37357   In the center of the Fire Tower, fourth floor
Loading room 37357 from database
curRoom.name: In the center of the Fire Tower, fourth floor
room.name: In the center of the Fire Tower, fourth floor
Fixing up exits
Moved from 37349 to 37357 in direction u
Current destination =  37357
Current return      =  37349
Fixed exit u from room 37349 to be to 37357
Speedwalk failed! Expected to be in '37357' but ended up in '37357'.
Speedwalk cancelled.
Fiendish USA Global Moderator #2
Quote:
What additional info can I provide that would be useful to try figuring this out?

You might start with the code.
Victorious #3
Figured out the problem - i wasn't ensuring that my room uids was converted to strings, so it was comparing strings to numbers.
Nick Gammon Australia Forum Administrator #4
That old trap! Leads to strange messages. :)