You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They use a dialog like the druid FPs but don't give a perfect location for the destination. Could you possibly assist @illiath? I can screenshot the dialogs if needed.
The text was updated successfully, but these errors were encountered:
So, quickly rechecking my code, check out Timer.lua, line 166, that starts the "Druid" flight path capture stuff. Originally, this code had hard-coded "target" locations because the druid start positions moved a little on the map, but I was able to decrease the resolution of the map x/y coordinates sufficiently not to impede the locations for any other points so that was removed. You might need to therefore add a new entry style that has them force-set.
That said, screenshots of the EFM display to show where it thinks the nodes are would be great.
Also what would be great is a dump of the node information for the node that "wanders". It might be possible to adjust for this, depending on the situation.
However, if the nodes move considerably, then this could not be adjusted for in the node settings and so each target point would need a new node definition, and so figuring out which node the user is able to fly to right now, and showing that information would require an additional abstration layer.
They use a dialog like the druid FPs but don't give a perfect location for the destination. Could you possibly assist @illiath? I can screenshot the dialogs if needed.
The text was updated successfully, but these errors were encountered: