Biggs datacron

"StarSon;c-2462856" wrote:

"iMalevolence;c-2462855" wrote:

"StarSon;c-2462853" wrote:

"iMalevolence;c-2462825" wrote:
The Commander Cody infinite loop was left alone ~4 datacron sets ago. Why was that one left unchanged during its entire run, but the Biggs one is too problematic and needs stripped from players mid set? It is literally the exact same affix (and this can be seen because this change retroactively changed the cody cron description on the .gg website).

I feel like you just answered the question. They fixed it to prevent future loops.

As I've mentioned, it's about the precedent they had already set. If the exact same infinite loop had been untouched for an entire set already, players should be able to safely assume that it won't be touched mid set this round.

Players knew this would loop under MM the day they announced the datacron set. CG should have immediately (within a day or two) made it very clear that they would be making changes to it to prevent that and then made the changes ASAP. This is not something that gets silently dropped on players 2 months after the set is released and after people have spent money/crystals and various datacron materials to acquire a biggs cron and upgrade biggs to R5 to use the cron.

Or maybe they didn't want to push a fix until they had it properly tested, since it was going to affect multiple datacrons?