I've been experiencing terrible pain in my ear since February and I've seen like 8 or 9 different doctors and none of them have any good idea why. Some days its more bearable then others and some days it's bad to the point where its impossible to get any work done. Dealing with this has made getting any work done much harder and slow then it would normally be. Currently I have three goals I am working on: 1)Create a new navigator that is asynchronous in nature 2)Create a new fate bot that will have: -specific logic for each of the different kind of fates instead of the generic logic we have now -rudimentary flying capabilities to get from fate to fate 3)Export all the currently used orderbot tags into a separate project and include them within the release to provide examples and a area where improvements can be imported from users My original plan for flight was to use a third party library for 3d navigation, but after signing all the NDAs and having several meetings the amount of money they wanted was just a crazy amount that we couldn't pay. It took the honorbuddy TEAM several YEARS before general flight was made available. And its not like we can just copy their work and add it to rb the system just doesn't work like that. Flying will come, just not anytime soon. If your impatient well I guess you could start a indiegogo or kickstarter and raise around 75000 usd and then we could purchase that library to use and have something out quicker otherwise your just going to have to wait.
Hey Mastahg, I'm sorry to hear about your ear problems. I understand how general flying can be a huge undertaking. Instead of general flight, I wanted to ask you if you think it would be possible to add an API call to elevate the character in altitude without regards to any 3D mesh or navigation, something similar to the player mover but for the Y axis. My hope is that instead of having general flight, perhaps reduce it to strict waypoints. I think this would be enough for many gathering / questing applications where you can script the path precisely.
This would be amazing, just a way to set the vertical tilt of the character alone if possible would be great. Just the API features by themselves would be lovely.
Taking off is a complicated issue in its self that i am working on. Gotta check that we can fly, gotta check if we are mounted, if we are mounted can this mount fly, if it can fly have we unlocked flying for this mount, if not do we have any mounts unlocked that we can use to fly, does that mount required the chocobo to be dismissed etc,etc etc.
For flying, I've found that ff14bot.Managers.MovementManager.MoveForwardStart() is working in the air and I've been able to get into flight mode with: code that should be used removed. -m All that I think is really missing is a ff14bot.Managers.MovementManager.SetFacing(theta, phi) to hobble together some rudimentary straight line flight. Then again, it might not be that simple since there seems to be boundaries the angle you're allowed to fly up/down.
I think we can check (nearly, unsure about the aetherytes) all that on the other side of the API, push comes to stove. Even a extremely (For the scope of the task, obviously) simple api consisting of: ReachSpecifiedY MoveWhileFlyingToXY would be an enormous help, and while i have no clue of how many pointers deep the commands are, it _should_ be a general issue of rotation and movement, and undoubtedly several orders of magnitude easier than general-purpose 3D nav. I'll look botty, and be probably unusable for fates, but would solve the issues with gathering.
I removed the code as I don't want something like that propagating. Thread.Sleep should never be used because we run inside a framelock. I am working on async take off and land functions that will do all the dirty work of checking if we are ready to fly etc. I don't even.
Woops. That was just code I ran in rebornconsole to test if the concept would work. I used an async calls in the tag that I put up. If it's any help, I've just found out that the 'draw/sheathe weapon' keybind will make you descend all the way.
Hey Mastahq, not sure how big a change it would be but is it possible to put a escape route wwaypoint into a profile for a gathering class which we define. If we get agro, it would run to that point to release the agro and then continue.
Thanks that's a nice idea, I'll look into it when I get around to cleaning up the rest of the tags so that they can be published along side the bot. As a status update I've got 3d facing taken care of along with ascending and descending without having to send keys to the window. I've got an appointment with a neurologist in the afternoon on Thursday but I'm going to try and get it done before then. As a note to developers who are creating custom tags if you could name your tags to avoid any conflicts that might arise when an official tag is added, that would be great. Ie i was releasing a custom flyto tag name the xml attribute something like FlyToMG or something like that so when an official FlyTo tag is released we don't have peoples profiles breaking.
Dude.. Unspoiled, Ephemeral, timed fishing, red gathering scrip, blue gathering scrip.. All the things!
Just to clarify flying navigation is no where near complete. Only the ability to adjust facing and height while flying will be added. This is useful to devs but you won't suddenly be flying around gathering stuff.
I've been using really long way points for long distance movement, but marking every possible landing spot with waypoints is a pretty big pain. Would it be possible to get something like ff14bot.Navigation.GaiaNavigator.CanNavigateFully(Clio.Utilities.Vector3, Clio.Utilities.Vector3, float) without a from argument? So we can see if a spot is landable? Or better yet something like ff14bot.Navigation.GaiaNavigator.MoveToRandomSpotWithin(Clio.Utilities.Vector3, float, [string]) that returns a location that's properly meshed so we can get a viable spot to land around a POI.
The nav server has no idea if a spot is landable or not. Theres also lots of tiny bits of meshed areas spread about along edges and what not.
