Quote EricMusco Quote: Originally Posted by Hey everyone,



I wanted to give everyone a heads up about the Cassus Fett's Armor coming out in the Pursuer's Bounty Pack on Thursday and an issue relating to Collections. There are multiple pieces to the Cassus Fett set, one of which is the belt. When the pack goes live on Thursday, the belt will not be required to complete the set in your Collections. (This is a bug, keep reading!)



The belt not being required for Collections will be fixed in Game Update 2.4 on October 1st. What this means is this:

Between Thursday 9/26 and Tuesday 10/1, you can complete the Collection of Cassus Fett's armor without the belt.

If you do not complete the Collection by 10/1, the belt will now be required to do so.

Note that if you complete the Collection by 10/1, after 2.4 hits if you pull the Collected set down from Collections, it will now correctly have the belt. Basically if you have interest in collecting the set, try to do it before Tuesday! Our bug will make it one step easier for you Hopefully that makes sense! Let me know if you have any questions. It is still intended that 2.4 will hit on 10/1, the dates above will move if the release date for 2.4 changes.



-eric





Additionally, I just want to add that I'm glad you guys took this approach instead of a) not mentioning it prior to the release and b) labeling it an exploit and punishing those that would capitalized on the bug. This is a much more customer friendly approach to a fluff item bug than most would expect.



Well done sir. Thanks for the heads up Eric! Also, pass my thanks on to whoever decision it was to NOT delay the pack release.Additionally, I just want to add that I'm glad you guys took this approach instead of a) not mentioning it prior to the release and b) labeling it an exploit and punishing those that would capitalized on the bug. This is a much more customer friendly approach to a fluff item bug than most would expect.Well done sir. JovethGonzalez Quote: Originally Posted by

After some investigation, it appears that there was some miscommunication between teams and this patch note was not intended to be included in this last patch.

