auto navigation

Bug #416119 reported by odbrazen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
leanlyn
Fix Committed
Undecided
Unassigned

Bug Description

easy manuevering is a must-have for most people. Allowing speedwalk macros just doesn't cut it.
[I'm ignoring the mapper.py module, as it is in a perpetual state of "almost done"]

Other clients use interactive GUIs to help players create maps. A GUI is a lot of work so instead I'm thinking of a simple module that includes a litany of
  1) start room desc
  2) start room <name>
  3) path to end room from start
  4) end room desc
  5) end room <name>
  6) path to start from end

As long as all the paths touch we can use the mapper.World class to pathfind from any <name> to any other <name>
Room descriptions would be treated as unique, and if you are in a known, named location the status bar would reflect that.

Tags: beta
Revision history for this message
odbrazen (odbrazen) wrote :

done in rev 126
@go_name('roomA', 'Room (e,w)')
@go_name('roomB', 'Room (n,w)')
@go_add('roomA', 'e', 'roomB', 'w')
#go roomB

So autowalking from the current [named] room to any other named room works as long as they share a link to some other named room. The pathfinder doesn't do any kind of magic so it will happily go North and then South if that is what the recorded path says. This won't be smarter until we add exceptions because there really are some places where North/South aren't reducable to a NOP.

Changed in leanlyn:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.