Original Post — Direct link
This is incredibly frustrating because on the PTS we made SEVERAL posts about this issue and nothing was done about it before this patch went live. And now i have to deal with one of the most annoying bugs that a DPS could deal with.

Certain 5 pc bonuses of sets are falling off. STILL. Like Deadly strikes... EVERY TIME i travel to a new area or go through a loading screen, my 5 pc bonus of deadly gets completely wiped. The only way to fix this bug is I have to COMPLETELY unequip deadly strikes, every single piece and then re equip the entire set. I havent even been playing Blackwood chapter for no more then an hour so far and ive already had to unequip and re equip deadly like 6-7 times.

PLEASE FIX THIS.
almost 3 years ago - ZOS_JessicaFolsom - Direct link
Hey @BrentBlemish thank you for the info. We are aware of this and actively investigating. What is the character name for the character you are experiencing this on? Also, what pieces do you have equipped and could you provide a few zone transition examples where you have had this occur?

Thanks!
almost 3 years ago - ZOS_JessicaFolsom - Direct link
BrentBlemish;c-7272230

My character Hugs N Pugs

The pieces that I have equipped are two daggers and jewelry. I have to completely unequip all of them and re equip them fully to get the 5 pc back.

Zone transitions are almost anywhere honestly. I traveled to Blackwood from a player home, I lost the bonus. When I logged in today I lost the bonus. After running around blackwood and went into a Oblivion portal tranistioning into the deadlands, I lost the bonus. When I started bastion quest line and walked into Deepscorn Hollow for his quest, I lost the bonus. So it's almost any transition honestly.



Hiya! :smiley: Thanks so much! Is this on PC-NA or PC-EU?

@PureEnvelope35 Thank you for the info. May we get a character name or two? We're taking a look at specific character set-ups as part of our investigation.

almost 3 years ago - ZOS_JessicaFolsom - Direct link
Thanks for the character info, @BrentBlemish and @PureEnvelope35! We've passed these along to Dev to help with their investigation of this issue.