[Ace]

I don't think you're updated if it's still happening.

[ateno]

I've been using it for a bit now and I think the only issue I'm having with it is that it takes too long to use Bloodletter. When you're using iron jaws and dots, you get so many bloodletters that become available, but the ACR module is taking so long to utilize them that you lose some in the process. Is there anyway to ensure that its checking/using bloodletter immediately as it becomes available?

I want to highlight this as a high-priority fix if possible - there have been so many times I need to spam click Bloodletter because the bot overlooked that it is up (usually at milliseconds as casting timers are near reset). This one alone is easily 100-200 encdps lost already.

Few other suggestions:
1. I feel that there are too many unnecessary toggles for Minuets - should just be On (which means bot will automatically uses whatever it feels best) and Off (which means player will have complete control). As of now I don't see why there needs to be an Off option when we have Manual, and also WM option (not sure what this does).

2. just wondering if it has a logic to prioritize Ballad over Requiem or not? For example, if the conditions to cast Ballad and Requiem are both met, which one will it uses?

3. For opener, if Minuets is already on, it seems that the bot still tried to re-cast it again, which is not optimal

4. Sometimes Barrage is up, and Empy Arrow is still used without Barrage being casted. It should be the case that Barrage is re-used as soon as Empy Arrow is up again

5. Sometimes Flaming Arrow is not re-used properly when it is up again - it is quite hard to capture the log of this one, as it happens during fights. I have to keep smashing the Flaming Arrow button to manually re-apply it

Other than those, awesome ACR :)

[ateno]

Whatever change you have made for Bloodletter - it's AMAZING! Thanks Ace!

[Ace]

I too don't like being so many toggles, but other people would disagree.
Song prioritization is Ballad > Paeon > Requiem.
The opener actually turns off WM for the first second and then kicks it back on mid-way, may eventually add some other options.
Flaming Arrow is a bit buggy after 3.4, bot is probably trying to internally cast it but the client refuses it, sort of a WIP there until the exact issue is found.

As you've already seen bloodletter/emp got some major overhauls in the last update due to some things that were mentioned and other things I noticed that I didn't like.

[crayfish]

I really like the opener change where you can see the opener currently being used and R/NR Can this be implement with other ACR opener?

[ateno]

Thanks for the awesome work Ace - I really like the changes to bloodletter / emp - no more smashing buttons now!

One thing I notice - that I am not sure is linked to the issue you highlighted with Flaming Arrow, is that after Opener, when both Internal Release and Flaming Arrow are up, it seems that the bot will use Flaming Arrow before activating Internal Release - you can probably test this with a dummy - just wondering if it can be fixed.

Also, just wondering if the bot should always activate CDs first before 1st shot on opener - I ask this question because sometimes I notice the bot does a Heavy Shot first, and it is not ideal as I want to activate the bot & opener when team's countdown reaches 2-3 without pre-pull the boss.

[Ace]

If it doesn't open with all 3 buffs, then it didn't execute the actual opener, most likely.
The opener button will actually swap to "Running.." and will show a (NR) "not ready" or ® "ready" next to it as of a few updates ago.

I'll have a look at IR.

[pig003]

Is it my problem or will the bot use the new "Supramax-Potion of Dexterity" (NQ / HQ) in its rotation when the potion switch is on? Thanks.

Edit: My fault. Seems okay now.

[pig003]

Not sure if it's just my problem or not, I found that the auto face feature is sometimes broken: the character failed to look back the original direction after using smart jaws or smart aoe (the target mob was in another direction when smart * was used). Also, the bot failed to look back the original direction even after the mob pull (I.e the character will keep on facing west even if he was walking north).

I have both the in-bot and in-game autoface feature on. I am using legacy control mode and game pad. The addon once worked perfectly before patch 3.4.

Please let me know if you need more info. Thanks in advance for your support.

P.S. I was using assist mode.

This also happens to me. You don't need to worry about it, it's only in your screen. To test it i brought my brother with me in a dungeon and he said i'm running fine even though it's happening like you said.

Thanks for your sharing. But facing the other direction after applying smart * sometimes also broke the rotation. Seems that's due to that the bot was not facing the mob it was targeting. Just my guess though.

Is there any chance that this autoface issue gets fixed?  I still encounter it quite frequently when the "smart" switches are on.

Although as optiblast said that it only appears on my own screen, there is a certain mechanic in A11S that the facing direction is the key of dodging an attack, and this facing-direction-bug made me unable to dodge the action and caused several wipes. And now I have to turn off the "smart" switches on during A11S.

Your help is much appreciated. Thanks in advance.

[Ace]

It won't be fixed until I can accurately reproduce it to understand what it is you guys are even seeing.
If somebody could get a video of the occurrence, it would help.