Picked this bot up yesterday, I have been very familiar with Honorbuddy over the past few years and happy to see this bot on the same platform. I have been using the atma plugin and noticed during fates, the bot doesn't avoid aoe attacks... Is there any setting to change this? Not avoiding them makes the bot look very bot like and also makes it tougher to solo some fates. Any help would be appreciated.
Since I am not a coder... Is this something that is even feasible to implement? Or should we just assume/accept that it's not happening (because it can't)?
It's certainly possible, but it hasn't been done yet. The location of ground spells in memory would need to be determined (they're not game objects like other things) and then avoidance code would need to be programmed. I certainly hope this is being actively developed because it's desperately needed, but it's not implemented yet.
I've seen people say it's not possible with FFXIV for some reason, but I don't know the technicalities. I honestly don't see why not when almost any other game I can think of has bots that are capable of it (WoW, D3, LoL, etc.), but I'm not a developer lol.
I mean maybe it's not possible but that would be very surprising... It might be difficult but it shouldn't be impossible (nothing should be impossible with enough effort). The client has to render the ground effect, so the data for where that effect is rendered has to be stored somewhere, as does its radius or cone or whatever it is. If that could be found we could theoretically calculate it's size, determine if we are in it's range or not, figure out the best path out of it, and then move. Probably a lot of work, but I think it's a very important feature.
I had a question here... Are we able to distinguish which way the mob is facing at all? My feeling is that, yes we are, because I noticed my dragoon will only use heavy thrust when behind a target. As such, I feel it might be nice to be able to make some sort of plugin that allows the bot to force you to try and be behind the target (when the mob is not targetting you since then it will obviously just turn). This wouldn't avoid all AOE attacks, but it certainly would avoid all cone and box type AOE attacks.
Yes, that should be possible. As you say the logic for when to use certain skills is already available. It would just have to be tired into the movement calls (although I don't know how heavy it would be with the way the bot currently requests paths from the mesh nav server). However, that would only avoid AoE when you're not the aggro target. You'd also have to throw in logic to not attempt to avoid when you're aggroed (otherwise the bot would just rotate around the mob constantly trying to get to the side/rear). It would be best if the bot could detect the actual AoE cones/circles, but who knows if that'll ever be prioritized. Also, I think it has more to do with the combat routine than the bot itself. Since Magitek development has ceased I doubt this bot will ever see such features (unless the secret combat routine currently being worked on comes out soon, but development just started as far as I know).
The only issues I have really come across (regarding AOE) is really bosses. I had to blacklist a few when I know I am not right there looking at th egame because it looks pretty silly running up to svara and getting my face melted time and time and time again lol. Most bosses seem to have a cone as their NASTY (one shot) ability, so I feel this would be useful. Does magitek actually do any of the movement? I assumed it was the fatebot. If it is the fatebot, seems like that would be a feasible option.
Another bot (not sure if I can mention others here) has AOE avoidance in at a very basic level. Far from perfect, but it's there. I'm not sure if they are reading the AOE field from memory or if its just going based off parameters entered from the skill being cast.
That's actually a concept that I didn't think of, but it's kind of genius. Something like this could be implemented immediately I would think? I would be happy to help gather information on it, sadly I am not a coder so it's not something I could help write.
