Ehm a problem.. Bot has stopped working.. Unable to let it start... View attachment 872 2014-06-13 10.46.txt
i start my game and when i try to open the bot after i press log in when the window where you put your key comes it just dissapears and nothing opens. Help would be appreciated
Its the same for everyone atm another Patch for FF14 was Pushed this morning just need to devs to update Reborn Buddy
Stuck in Southern Thanalan Starting at [20:25:16.194 N] Current fate set to F8450A0 Name:Bump and Grind Id:456 Icon:Boss ObjectId:E0000000 Location:<93.99692, 6.344424, -548.3104> TimeLeft:00:13:28.8061652 Radius:50.42039 Progress:10 Level:28 MaxLevel:33 Status:ACTIVE Ending at [20:26:49.839 N] Stopping the bot. Reasonushed the stop button. The fate is in a cave and the bot runs past the entrance and up a mountain then turns around and gets stuck on a fence.
I like the new FATE bot, and how smooth it is to run from FATE to FATE. Seems smoother than other bots out there. However there is something weird when hitting the outside circle of a Fate when reaching it. My Character seems to run back for a split second at times. It isn't happening with all FATE's. Also, when mobs move around, and i have to chase them, it does the same thing, where it will move forward and backwards very quickly till it reaches its target. I tried in Middle La Noscea with Dragoon. View attachment 5092 2014-06-13 14.21.txt edit: also the transition from FATE "The Boy who Cried Jackal" to "The Truth Is Out There", My Character pauses and doesn't continue to proceed to the next FATE in the same location until I force it to hit something, then it will respond. Also, is there a way for the FateBot to recalculate in the middle of pathing to a FATE if the one pops up closer?
Log 1: FateBot_Coerthas_01 - Pastebin.com Log 2: FateBot_Coerthas_02 - Pastebin.com Thank you again for all the work you've put in so far. The Fate Bot is running much more smoothly than I expected and I'm very pleased that it's coming along so well. These are logs doing Fates in Coerthas for about 3-4 hours. - I noticed that the refresh button in the bot settings window is updating MUCH better than before, but it still does not always update with the correct fates or ALL the fates. I'm sure this is something you are still tweaking, but I wanted to make the observation. - In Coerthas, I have the settings to "Return to Aetheryte" but this setting does not work. I have not tested other areas and have not fully tried using a "Set" coordinate to return to". - As Becto said two posts above me, there are times when moving to the next fate or a mob that the character will move forward then jerk backwards very quickly then proceed to move again. It does this over and over about every half second until it reaches it's destination. - Sometimes, while in a fate with multiple mobs, it will attack the first mob just fine, kill it, then stand there "ready for action", but it does not move on to the next mob. - If possible, I'd like to see an option, in Bot Settings, similar to the current option of "Only attack boss fate if % is at x", but instead of just boss fates, I'd like to include this to ALL fates. In popular areas, like Coerthas, it might be a great way to stay with the group so to speak and make the bot more efficient. - Lastly, and again as Becto suggested, rerouting for newly popped fates nearby after it's already decided a route would be great, or even possibly a way to prioritize fates. Something simple, like allowing us to give fates a numerical value that it then will judge which fate to do first. Great work, thank you again.
Have not touched this at all. Can't reproduce it not working anything but 100% correctly. If you can find a zone or fate that does not work more often let me know. For these I need more information. If this was present in those logs, can you provide a time? I need information like what zone and fate and how was the bot positioned in relation to nearby mobs. Was the POI set to kill and it was just standing there?
Version 140 Code: Overall: Log when statustext changes for enhanced debugging Fatebot: Performance improvement in combat targeting.
In southern Thanalan doing Fate Downwind I have a log where my Pugilist would stutter going back and forth to the mobs, he also does it when running between mobs to kill. It starts around [20:25:09.428 D] [POI Set] Type: Kill and I stopped the bot after the fate was done. Also there is a fate called Harder, Bigger, Faster, Stronger in Southern Thanalan that it is a slay monster Fate that it won't even go to it was up when I started the bot and was on the list.
Version 141 Code: Increased the range a target has to move before a new path will be requested. Please let me know if those helps resolves the issues with stutter stepping as melee characters as I have not been able to reproduce the issue my self.
Ok I try to melee now and I'll let you know in one hour or two. In fact the bug is simple when you fight against the elemental or firefly style, fighters do not stick to the mob and finds himself too far to fight. sorry for my bad english I use google translation.
With the newest fate bot, my character will always stay mounted on his chocobo while waiting for a fate. This is a bit of a problem in high level areas because if an mob aggros you the character will not attack back and die. The "go back to aetheryte" after a fate function doesn't seem to be working either.
Only problems Ive been having with the FATE bot in the last 2 days is requesting/generating paths cause the character to appear to run/mount run backwards then forwards repeatedly. (Still happening on ver 141, clean install) Here is an example that happened just right now in a Central Thanalan FATE where It ran from a killed mob to the next mob where it requested/generated paths 5times for a verrrrry short distance that made it kinda look like i was moonwalking. [17:49:17.186 N] [Magitek] Casting Stone [17:49:17.186 D] DoAction Spell 119 0x400078E5 [17:49:18.605 V] [Poi.Clear] Reason: Invalid Combat Poi [17:49:18.615 D] [POI Set] Type: Fate [17:49:18.642 D] Poi: Type: Fate (Wrecked Rats) | Idle [17:49:18.646 D] Requesting path on 141 from <-88.18412, -10.91824, -20.23861> to <-83.7607, -11.35006, -51.94866> [17:49:18.743 D] Poi: Type: Fate (Wrecked Rats) | Moving to fate [17:49:18.826 D] Generated path to <-83.7607, -11.35006, -51.94866> in 00:00:00.1810257 ms [17:49:18.833 D] Moving to next hop: <-83.96667, -12.06528, -30.68333> (Moving to fate) D: 11.32231 [17:49:21.877 D] Poi: Type: Fate (Wrecked Rats) | Idle [17:49:25.127 D] [POI Set] Type: Kill [17:49:25.137 D] Targeting Qiqirn Shellsweeper 0x400078F0 0x119C8240 [17:49:25.167 D] Requesting path on 141 from <-85.4746, -12.33198, -26.94886> to <-106.3448, -8.373343, -7.259936> [17:49:25.213 D] Poi: Type: Kill (Qiqirn Shellsweeper) | Line of Sight [17:49:25.348 D] Generated path to <-106.3448, -8.373343, -7.259936> in 00:00:00.1812849 ms [17:49:25.366 D] Moving to next hop: <-91.48578, -10.00269, -15.4858> (Line of Sight) D: 13.15149 [17:49:25.523 D] Requesting path on 141 from <-85.65916, -12.27314, -26.59693> to <-104.482, -8.667408, -8.626779> [17:49:25.705 D] Generated path to <-104.482, -8.667408, -8.626779> in 00:00:00.1823507 ms [17:49:25.797 D] Moving to next hop: <-91.48578, -10.00269, -15.4858> (Line of Sight) D: 12.05654 [17:49:26.035 D] Requesting path on 141 from <-86.63599, -11.96176, -24.73417> to <-102.5727, -8.948104, -10.04724> [17:49:26.218 D] Generated path to <-102.5727, -8.948104, -10.04724> in 00:00:00.1832828 ms [17:49:26.310 D] Moving to next hop: <-91.48578, -10.00269, -15.4858> (Line of Sight) D: 9.909891 [17:49:26.468 D] Requesting path on 141 from <-87.40584, -11.71635, -23.26611> to <-100.6187, -9.212631, -11.48431> [17:49:26.628 D] Poi: Type: Kill (Qiqirn Shellsweeper) | Moving to pull range [17:49:26.655 D] Generated path to <-100.6187, -9.212631, -11.48431> in 00:00:00.1866576 ms [17:49:26.747 D] Moving to next hop: <-91.48578, -10.00269, -15.4858> (Line of Sight) D: 8.22589 [17:49:26.867 D] Requesting path on 141 from <-88.07328, -11.50358, -21.9933> to <-98.65877, -9.363503, -12.92348> [17:49:27.046 D] Generated path to <-98.65877, -9.363503, -12.92348> in 00:00:00.1776746 ms [17:49:27.153 D] Moving to next hop: <-91.48578, -10.00269, -15.4858> (Moving to pull range) D: 6.738871 [17:49:27.275 N] [Magitek] Casting Stone [17:49:27.275 D] DoAction Spell 119 0x400078F0 [17:49:27.326 D] Requesting path on 141 from <-88.76315, -10.94896, -20.67773> to <-96.78571, -9.439458, -14.29869> [17:49:27.336 D] Poi: Type: Kill (Qiqirn Shellsweeper) | [Magitek] Moving in Range [17:49:27.437 D] Poi: Type: Kill () | Idle [17:49:27.497 D] Generated path to <-96.78571, -9.439458, -14.29869> in 00:00:00.1709060 ms [17:49:27.538 D] Poi: Type: Kill (Qiqirn Shellsweeper) | Idle [17:49:28.549 D] Poi: Type: Kill () | Idle [17:49:28.650 D] Poi: Type: Kill (Qiqirn Shellsweeper) | Idle Few more logs about this @ https://www.thebuddyforum.com/rebor...es-bot-will-look-backwards-then-forwards.html One deals with (Moving to Fate Range) req/gen spam and (Moving to Target Range, causing stutter stepping) I've had the bot sit mounted in the zone where little ala mihigo is ~ and get beat by a pack of mobs... dont have my log for that encounter anymore but pretty much while it was happening it was only saying > There is no fate we can currently tackle | Idling. I think this might have been a zone where the Return to Ath wasn't functioning either as when there was no fate ready to kill it would idle in the exact spot where the previous fate ended. Will have to add that log in if it happens again.
