Nik-Potokar / XIVSlothCombo

XivCombo for very lazy gamers
GNU General Public License v3.0
254 stars 306 forks source link

[VPR] Attack actions disabled when Noxious Gnash abilities are not learned yet #1540

Closed NikaLeets closed 1 month ago

NikaLeets commented 1 month ago

This issue affects at least Simple mode Single Target, Advanced Mode Single Target, and Advanced Mode AoE, but based on what I've seen, i'm pretty sure Simple Mode -AoE will be impacted as well.

This issue is when Dread Fangs is not known yet (character level < 10) or Dread Maw is not learned (character level < 35), a disabled Dread Fangs/Dread Maw is offered instead of Steel Fangs/Steel Maw. This makes these features completely non-functional < lvl 10 for single target and < lvl 35 for AoE. In the advanced modes, you can work around the issue by removing the Noxious Gnash check in both advanced modes, but it is always present in simple mode.

This is problematic in PotD solo runs while in the first 2 PotD floor sets.

Kagekazu commented 1 month ago

image what are u talking about?

I am in PoTD floor 1, and it just spams steel fang.

Are u sure u are on the current version of 3.2.0.2?

Kagekazu commented 1 month ago

just did the first 5 floors of PotTD

1-5 it spams steelfang 5-10 it does steelfang - hunters sting 10+ it incorporates Dreadfang.

can u show a screenshot of ur Repor URL? so that we make sure ur on the correct Sloth version.

NikaLeets commented 1 month ago

I will verify and show screenshots as soon as Dalamud re-enables after the patch. I'll make sure to post Sloth version on future defect reports.

NikaLeets commented 1 month ago

That was quick. Dalamud is back up. I was running Sloth version 3.2.0.1. I just confirmed that this issue was present on 3.2.0.1, but is fixed on 3.2.0.2. Thanks!

Kagekazu commented 1 month ago

current version of sloth is 3.2.0.2. image

please update and see if it happens again.

Kagekazu commented 1 month ago

That was quick. Dalamud is back up. I was running Sloth version 3.2.0.1. I just confirmed that this issue was present on 3.2.0.1, but is fixed on 3.2.0.2. Thanks!

alrighty, no problem! if anything still is weird lemme know and ill see to add it to my bugfixes