Hello! I have been testing out RB for the better part of the last two days, and fully intend to purchase a key as soon as my three day runs out! Nice work on this bot! So far, Fatebot has worked wonderfully, no issues whatsoever. I wouldn't mind it to attack non-blacklisted boss fates before they've been started by someone else, but hey, I'm not a developer. I am having issues with Combat Assist though, I've tried to run the Kupper, Kupo, RebornCO, and Ultima combat routines, with some luck, but nothing that would pass as usable. Some info: I am a Lalafell Current Class: Ninja, though I have tried Bard as well Current Levels Impacted:25 - 32 Places attempted to use: Dungeons, FATES, Guildhests and regular mob grinding In each instance, I start up the bot, select one of the listed combat routines above, and run combat assist. Everything starts up like it should, just like I'm used to with Fatebot, but once I initiate combat with a mob, I begin to receive the error, "Target is out of Range" or "Target not in Range". This error is received regardless of where I am standing and regardless of the skill I am attempting to use, including ranged attacks of ranges up to 25yalms. I am able to manually attack the mob, but ONLY if I begin to run around it, jumping and varying my distance from it, from 25y to directly underneath of it. Regardless, I continue to receive this error throughout the entire fight. I could very possibly be doing something wrong, but, searches have not really been fruitful. That being said, one of the potential "fixes" I've seen was to use Ex Combat Assist, I have it downloaded and installed to it's proper location (I think - /RB/BotBases/ right next to RaidBro) but I do not know how to force it to be loaded over RaidBro. If that might work, could someone lay some instructions for that for me please? Thank you for any help! Edit: Logs! >_<
looks like my patrol has a null error I'm having trouble telling exactly what your problem is/what you want. Is your only concern that you are seeing an in game error message and besides that the bot is behaving properly. Are there times when it's not attacking when it should be?
I would definitely suggest you use ExCombatAssist over CombatAssist. That's what I use for dungeons and it works great with most combat routines. I would suggest you try and fix your compiler errors first, you might have two ExCombatAssist copies somewhere in your RB folder, the AtmaHunter plugin is out of date in regards to the API, and Patrol is giving you a few problems. It might be a good idea to try out ExCombatAssist without any other plugin enabled. To use ExCombatAssist you just select it on the BotBase dropdown menu just like any other bot base.
The issue was when I initiated combat with a mob, I was unable to continue combat autonomously through Combat Assist. It was indeed not attacking when it should have been. As a note, patrol is working perfectly well with FateBot, and I assumed that is the only place it is supposed to work. No worries there. I did as you suggested and looked over my folder structure. There was an extra folder adding one too many layers for ExCombatAssist to work. (Newb, newb, newb...) I removed the folder, and was able to select the proper BaseBot upon restarting the bot. Still no dice. However! I wondered since FateBot was working so well, if it might be something even simpler than the bot itself. So, I decided to try tweaking some in-game settings, specifically turning "Automatically face target when using action." on. After a couple of pulls, I have not noticed anything going crazy! I'm currently waiting for a dungeon to pop, but that looks like it might have fixed that error for me. EDIT: Ensuring ExCombatAssist was properly installed and that the in-game option "Automatically face targets when using action" is turned on, solved this problem for me. Thank you for all your help!
