FlightPath is a navigation aid of a different sort. Instead of displaying direction and heading with arrows - whether that be the top-down style in the minimap, or the GPS style commonly seen in other addons, FlightPath shows this information in a HUD-style "tape" compass, with heading and waypoint indicators.
Currently, in this proof-of-concept phase, FlightPath does not make use of any commands or options, and will automatically pick up and display any changes in the "active" quest (i.e. the quest location the yellow minimap arrow is pointing to). However, as development continues - plans include the ability to add custom (ordered) routes, as well as individual points, command support, and options such as size, color, and position.
Requests and feedback are always welcome, and will always be seriously considered. However, this does not necessarily mean that every suggestion will be implemented. It does generally mean that as long as it a) is possible, and b), fits within the design goal, that it will most likely will be implemented.
Of course, while not quite as eagerly anticipated, bug reports are welcome as well - and will be addressed as time permits. In this case, any information you can give about the situation where the bug occurred, as well as the error message, will speed this process up considerably. Remember, unless I can recreate it, it's exceptionally hard to fix.
Currently, in this proof-of-concept phase, FlightPath does not make use of any commands or options, and will automatically pick up and display any changes in the "active" quest (i.e. the quest location the yellow minimap arrow is pointing to). However, as development continues - plans include the ability to add custom (ordered) routes, as well as individual points, command support, and options such as size, color, and position.
Requests and feedback are always welcome, and will always be seriously considered. However, this does not necessarily mean that every suggestion will be implemented. It does generally mean that as long as it a) is possible, and b), fits within the design goal, that it will most likely will be implemented.
Of course, while not quite as eagerly anticipated, bug reports are welcome as well - and will be addressed as time permits. In this case, any information you can give about the situation where the bug occurred, as well as the error message, will speed this process up considerably. Remember, unless I can recreate it, it's exceptionally hard to fix.
