[REQUEST] Making possible to access current MoveTo destinations.

[strix]

Would it be possible to make movement destinations accessible for developers?
The only "wannabe" i found yet is Bots.ArchaeologyBuddy.ArchBuddy.CurrentDigsite.Location.

The purpose is to make HB travel with Hearthstones/Teleports/Death Gates, i've just made plugin that uses Hearthstone for Archeology and looks like it's working fine.
Just gotta add at least basic config before release and maybe Teleports/Death Gates.

 

[CodenameG]

Would it be possible to make movement destinations accessible for developers?
The only "wannabe" i found yet is Bots.ArchaeologyBuddy.ArchBuddy.CurrentDigsite.Location.

The purpose is to make HB travel with Hearthstones/Teleports/Death Gates, i've just made plugin that uses Hearthstone for Archeology and looks like it's working fine.
Just gotta add some basic features and Teleports/Death Gates.

its generated on the fly. i dont think what you want, is going to work unless archaeology buddy was changed to serve that information up somewhere else where other api can get to it.

 

[strix]

Well, when you call MoveTo, FlyTo or whatever, you specify the final destination.
It could then easily get saved into some public variable.

I might be wrong, but i think i saw all the CTM points to reach that final destination stored in array for some kind of movement.

 

[highvoltz]

Make a class that extends Styx.Logic.Pathing.MeshNavigator, override the MoveTo(WowPoint) method and capture the destination point (and pass the WoWPoint to the base MoveTo() ). make an instance of it and assign it to Styx.Logic.Pathing.Navigator.NavigationProvider.

 

[no1knowsy]

@ Strix - If you are looking for a Path-Finding Algorythm... an implementation of A* would work somewhat well. But instead of checking distance left to end point, you'd check if your current point can link back to your start point, and if that cost would be higher than keeping your currently worked path.
I was thinking about working on this, but for my simple uses I didn't need it.

 

[strix]

Well, when you call MoveTo, FlyTo or whatever, you specify the final destination.
It could then easily get saved into some public variable.

I might be wrong, but i think i saw all the CTM points to reach that final destination stored in array for some kind of movement.

I still cannot override it for Flightor, where it would be quite useful.

 

[highvoltz]

I still cannot override it for Flightor, where it would be quite useful.

The problem is flightor doesnt use NavigationProvider so unless you can convince Raphus to have flightor use NavigationProvider or make the destination public you're stuck with one dirty method, using reflection to discover the private destination WoWPoint that Flightor uses ( assuming it has one)