Just finished merging in AtmaHunter into the plugin and made a option for it. Figured it made sense to have one supported plugin to do both. While that is off running and testing, looking at the possibly of checking a hotspot. Should be able to figure something out there. On the second point of the starting and stopping the bot, I would probably stay away from doing that and rather fix any bugs found. On the third point, will look into that for sure. Thanks for bringing these up.
It's my pleasure. Figured the hotspot would alleviate the nav logic issue simply, the restart would clear any issues with the bot getting stuck in a loop, and the FATE was simply a matter of not having to stand there and wait for someone/a timer to start one fate, wait for that to complete, then start ours. Just a time deal. I'll keep looking for those little things like that, but like I said, plugin is well done and I am glad that you two have successfully encouraged me to complete at least one weapon before the expansion. NOTE: I've been watching the POI, and it appears that some of the profiles are set to grind while true until the plugin itself catches them, which I think is the proper way to do it. But, some of the profiles are while character level < 51. While not an issue right now, it will be once the expansion drops if people decide to use the plugin then. Just another 2 cents. Keep up the good work!
Edit: Nvm.. I'm an idiot. For people who wanna use Fate bot again after using this plugin, be sure to manually clear the "this fate only" selection in FATE Bot!! Also, I left Enmity of My Enemy up for like 5+ hours, any chance there's something broken with that one?
I will fix that. On unloading the pluggin will clear the fate. On the enemy fate it probably never popped as the prerequisite fate was probably never popped. Working on seeing how I can force pop that if the npc is there.
For enmity of my enemy there are actually 2 fates, this is the second fate so it would be awesome if you could fix it so it will take down the pre req fate "enemy of my enemy" and then move onto enmity fate. Also on a side note I've noticed most if not all of the enemy groups are killing 11 mobs instead of 10 before teleport, its not a big deal at all, but just wondering if you might be able to fix wo breaking it? (If its risky I don't mind the extra mob) also really looking forward to skipping mobs that aren't target mob. You've made great progress on this, keep up the awesome work!
So after enemies on Skyfire II, rather than going to Aleport for Breaching Southtide Gate it went to South Thanalan for Heroes of the 2nd FATE. Going from left to right its, Breaching Southtide Gate, Heroes of the 2nd, and Air Supply. Anyway order doesn't matter much, my problem was it made it to heroes, waited 10 mins and it killed stuff OK when fate was up, but then it went back to waiting for heroes of the second rather going to next fate location and waiting. log attached. Also Stop/Start and relaunched RB and its still stuck on heroes, even cleared out the FATE B This fate only thing before restarting. So there's a problem somewhere, haven't had this issue with fates on other books, it just autoran through all 3 after enemies no prob.
There are some FATE that start only when we talk on npc that show on location, like: - Schism - Tower of Power - The Ceruleum Road
I can verify I experienced the same issue as dwight for Skyfire II. 11 Mobs: Not an issue But the switch to FATEs went to Heros first and even after completion returned to try again. EDIT: After completing Breaching the South Tidegate, starting the bot again took me to North Shroud to await Air Supply. Where it successfully completed the FATE, telelported to Limsa and exited the Plugin.
Code: SkyfireII.Add(11, "Heroes of the 2nd"); SkyfireII.Add(12, "Breaching South Tidegate"); SkyfireII.Add(13, "Air Supply"); By changing the order here, we should be able to make them go in whatever order you want, read below, you'll see that I think the two problems are actually quite linked! :X Code: SkyfireII.Add(11, "Breaching South Tidegate"); SkyfireII.Add(12, "Heroes of the 2nd"); SkyfireII.Add(13, "Air Supply"); As for it verifying it... Not sure, it might be trying to verify completion based on having completed "Breaching South Tidegate". I'm not going to pretend I fully understand, but I think the zodiac stuff is largely controlled by the API, Heck, I don't fully understand what the API is really comprised of, but that's neither here nor there. There's a good chance the API is what detects when to move on to the next FATE, and that the plugin is only really responsible for telling it which FATE to go to. With this in mind, It isn't going to do anything except "11" or, Heroes of the 2nd -- that is, until the API detects that "Breaching South Tidegate" is completed. I think I have a pretty decent understanding of it, and it's more difficult to put into words than it is to understand, unfortunately. On a Side note, I'm sure nishalp understands this much better than me, because he did build all this from the ground up. I'm not explaining this to him, it's more for other people. It would be great if I could get confirmation on if what I said is more or less correct, though. TL;DR, The order is probably very important to the triggering of going to the next FATE.
Yes, I noticed this and I believe this is because the game is not registering the final kill on the exact time you kill it. In the mean time, the bot has already created a target kill job for the next mob based on order bot. So its just finishing that up.
Yes, I am currently working on putting some hooks to pop the fates. In fact for The Enimity of my Enemy is done to the point where it pops the pre-req fate but I am having a few minor issues once it is popped to go into the fate. But hopefully soon this will be fixed. I can then use the same hooks to go pop the above fates.
You are correct Tinytox. The main problem is we dont know what fate belongs to which status so that why the dictionary is there which tells us that mapping. So in the end the ordering is very important. Lets take a example. We are ready to do the first fate. The dictionary says the fate is abc so it goes to that fate. It waits for the fate and when its done it checks if the API returns that Fate1 is done. If abc is not the fate mapped to Fate1, then it will not be marked completed and keep doing the same fate again and again.
So basically you just had this out of order and that's why it didn't go to the other fates? I'll just manually fix it for now and see if that resolves. Thanks Tiny
Another Fate that is a pre-req Fate is Gauging North Tidegate / Gauging South Tidegate which need to be killed before the respective Breaching Tidegate will spawn. There are probably others, but these are 2 I know have enemies before the boss FATE spawns. So it would be awesome to have this able to complete the pre-req FATEs to ensure the true FATE pops if nobody is killing them. Thanks!
