v1toor that means you are using a different combat routine than Ultima; That is a symptom of using Kupo, Cupper, or Magitek. Try deleting those folders from your CR folder and try again.
Hi! I have been loving this Combat Routine but was wondering if it would be possible to add in one small feature. Could you please add a checkbox somewhere that would enable an option of "Use Companion" for summoning chocobo companion? I find it really helps to have him out when leveling alt specs while running FateBot. Thank you very much for an awesome Routine, has been making this Bot work hard!
Ingvar as soon as you click combat settings the very first option is "Summon Chocobo" and select stance. If you don't see it try downloading the latest version.
Are you planning to add all the options from Magitek's BRD profile? (Don't DoT list, AOE/don't AOE etc...)
Thank you for understanding that I was talking about SCH. I'm a bit absentminded at times to include important information like that. The only reason why I like Bio being used first with Fatebot is because with a casting class it's hard to get enough DMG output during busy times to get gold in some fates. At least with Bio I can get a claim and when it's killed that goes towards my gold target. The heavy effect from Miasma has never really been a benefit because everything dies so quick in Fates and Dungeons. With Magitek I set my character to 18 yalms to avoid certain spots in Coerthas to where I'm within the max casting range but I'm close enough to avoid an obstacle. At that point the bot starts casting and when the cast doesn't go off because of LoS it just stands still. The back-up targeting may have to be the fix because this issue has been brought up to Mastahg before if my memory serves me right. Thank you again.
Fate contribution actually isn't affected by damage done or mobs tagged, only the number of actions you do on valid targets.
Now that makes Bio even more essential for Fatebot then. When you target a mob that's almost dead an instant cast is more beneficial.
Right now I have the check-marks for all the skills I don't have logic for disabled (so people don't get confused by checking them and wondering why they don't work). I was going to hide the checks altogether but then the form looked really weird with a bunch of gaps/empty space lol. Sorry for the confusion. Those skills willbe added in the future. Yeah today was crazy, sorry about that. Paladin should work properly now. Let me know if you still have any issues with it. According to that Reddit post, it's better to include Spineshatter Dive in the PS rotation now. If anyone says different they're probably quoting out-dated info (from before the 2.4 Dragoon buffs). Before 2.4 it was definitely better to not use PS with Spineshatter according to all the info I've found. As for HT/Phelbotomize, I've changed the rotation around a bit but I dunno if it'll fix the situation you're describing. What do you mean put them back-to-back? Isn't that in control of the user (HT will only be cast if you're flanking, so you could just not flank until you're ready for HT to cast)? They're both set to refresh when they have 4 seconds or less left on them though. I could try changing the logic to have one refresh sooner/later to stagger them better (changing one of them to 2 seconds or 6 seconds or etc.) if that would make any difference (although that might put them at even more of a risk of dropping/clipping)? Thanks for the report and sorry about that. It looks like there have been all kinds of issues today. I think everything should be good to go now. Let me know if you have any more issues. Same as above. I think I've fixed the problem that was causing this issue. Try it again when you get the chance and let me know if this is still an issue for you. Good news, it's already part of the CR! Click on "Combat Settings" in the bot and it should be the first thing you see (Chocobo Settings on the Ultima tab). I don't know if I can claim that I'll add EVERY option from Magitek, but the goal is to add as many features as possible going forward (of course I can't make any promises on when, but someday soon hopefully). Spell wise, I suppose you're right. Almost every other class/job in the CR is using an instant spell (when possible) to pull. I've switched Arcanist/Scholar/Summoner over to Bio (when possible, it will cast Ruin occasionally instead if it thinks Bio isn't valid for whatever reason) for now and we'll see if that works better for everyone. Thanks for the feedback. As for the LoS issue, yeah hopefully we can get that under control soon. My movement logic resolves LoS issues with the Current Target no problem, but it's not as simple to get it to resolve PoI LoS issues (at least not with the way my logic is currently setup). I'll have to build something special if mastahg doesn't come through for us. I'll try to get on that ASAP though just in case.
I realize you use CoRoutines and not TreeSharp, but here's some TreeSharp code you could modify? Code: new Decorator(ret => Poi.Current.Unit != null && !Poi.Current.Unit.InLineOfSight(), ff14bot.Behavior.CommonBehaviors.MoveTo(r => Poi.Current.Unit.Location) ), Would that not be fairly easy to implement? I dunno, I don't use CoRoutines.
Yeah, the problem is I only call movement on Cast. So if I'm not trying to cast (which I shouldn't be unless I have a CurrentTarget), I'm not moving. I'll have to figure out where the best place to put the secondary move logic would be (I have an idea I'm testing right now actually). Thanks for the code though. I'll see if Poi.Current.Unit works any different/better than Core.Target.
Is the monk routine working for anyone else? Bard and Ninja are fine for me but monk only casts off-gcd abilities and touch of death.
New version. Fixed some formatting errors and should have improved the overall performance of the bot (gotta squeeze out every drop of DPS lol). Also should have eliminated any (rare) undesired behavior, other than the movement issue discussed above (will try to get that taken care of tomorrow provided there aren't 10 more bugs to fix lol). Try the newest version and let me know if that changes anything for you.
Fatebot is still having some errors. Mainly, it will run my THM to fates, but now it will just stand their until something aggros it, and then engage. View attachment 8600 2014-12-04 08.05.txt Note: On diff. character on SCH I did not have this problem. So it may be specific to certain classes/jobs.
Sorry about that. It looks like some of my reformatting broke it lol. While I was fixing it I made a bunch of enhancements as well, let me know how it works for you. I think this might be related to the movement issues that mastahg patched today. Using the newest version of Ultima and Reborn, are you still having the issue? Also it looks like you're getting a few errors from the Eclipse-HealBot botbase and AtmaHunter plugin. I doubt they're the cause of the issue, but you might wanna remove them to improve performance.
Should I be able to select cross-class skills in the menu? Because none of the boxes are clickable. It selected some skills itself which I don't even have cross-classed.
Oh I did remove those plugins in my main folder. I own several copies of RB and forgot to remove them or update them in my secondary folders. I'll test it out and get back to you.
Would you be looking into improving your ninja dps rotation/opener anytime soon? I'm not saying yours is bad, it seems fine. i just feel it can be improved. Possibly something like this may help? https://docs.google.com/document/d/1kbBiOzDNxB_nTROQ_NdoWnNmoGAtuD0I6n-XR24tY0Y/preview?sle=true Also, if possible, would an option to not use assassinate be possible? Thanks.
