I first noticed this in the 4.1.0.0019 Beta build. I posted about it in the Patch Beta subforum, but nobody seemed to notice. (Ya'll have been busy lately for some reason...) It's still a problem in my save in the current build, so I'm bumping this up to the live-version Tech Support forum.
Aloth, in this save, is a Spellblade. I took "Strike the Bell" and "Break the Bell" from his Rogue ability tree to try them out. After playing a little while, I noticed that enemies were getting Dazed when they shouldn't. The enemies' status told me that they were affected by Break the Bell, even though I had only used basic attacks on them. Turns out that all normal attacks with 2-handed weapons were applying the "Dazed" affliction as if I had spent the Guile to use Break the Bell. With ranged weapons, the +3 PEN of Strike the Bell is added. (Haven't tried one-handers, but I'm guessing that the DoT effect would proc.) The attached screenshot shows that Break the Bell is on Aloth's character sheet as a persistent effect, rather than just as a useable ability.
At that point I reported the issue in the thread linked above, then respec'ed Aloth out of the ability to avoid exploiting the bug. That removed BtB as a useable ability, but the persistent effect remained. He still Dazes on every swing of his Pollaxe (or Spirit Lance).
I tried to reproduce this by rolling up an NPC Rogue with the ability to see what happens. (The result is "BreakerTwo" in the party in the save linked below.) Everything looks normal there-- Break the Bell shows up on the character sheet as a useable ability, not a persistent effect, and it only functions when used from the Guile-abilities taskbar. This leads me to believe that it was some kind of interaction with Wizard abilities that started this happening.
Here's a Drive link with a save. It's from after I respec'ed Aloth, but the thread linked above has a link to a different Drive folder that includes a save from before the respec.
Question
Enoch
I first noticed this in the 4.1.0.0019 Beta build. I posted about it in the Patch Beta subforum, but nobody seemed to notice. (Ya'll have been busy lately for some reason...) It's still a problem in my save in the current build, so I'm bumping this up to the live-version Tech Support forum.
Aloth, in this save, is a Spellblade. I took "Strike the Bell" and "Break the Bell" from his Rogue ability tree to try them out. After playing a little while, I noticed that enemies were getting Dazed when they shouldn't. The enemies' status told me that they were affected by Break the Bell, even though I had only used basic attacks on them. Turns out that all normal attacks with 2-handed weapons were applying the "Dazed" affliction as if I had spent the Guile to use Break the Bell. With ranged weapons, the +3 PEN of Strike the Bell is added. (Haven't tried one-handers, but I'm guessing that the DoT effect would proc.) The attached screenshot shows that Break the Bell is on Aloth's character sheet as a persistent effect, rather than just as a useable ability.
At that point I reported the issue in the thread linked above, then respec'ed Aloth out of the ability to avoid exploiting the bug. That removed BtB as a useable ability, but the persistent effect remained. He still Dazes on every swing of his Pollaxe (or Spirit Lance).
I tried to reproduce this by rolling up an NPC Rogue with the ability to see what happens. (The result is "BreakerTwo" in the party in the save linked below.) Everything looks normal there-- Break the Bell shows up on the character sheet as a useable ability, not a persistent effect, and it only functions when used from the Guile-abilities taskbar. This leads me to believe that it was some kind of interaction with Wizard abilities that started this happening.
Here's a Drive link with a save. It's from after I respec'ed Aloth, but the thread linked above has a link to a different Drive folder that includes a save from before the respec.
https://drive.google.com/open?id=1mnrCJE8T-ppzyVY3DqvMuNtp8oc87-w5
1 answer to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now