Biggs datacron

"iMalevolence;c-2462862" wrote:

"StarSon;c-2462860" wrote:
But if the goal is to fix it for all future datacrons that use this, why wait? Because you wanted them to for your benefit isn't really a good reason.

Please, let me redirect you to one of my previous posts (that was directed at you) that explained this already.

"iMalevolence;c-2462855" wrote:
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.

No, I understand why you (and others) want them to wait. I haven't yet seen why those are compelling reasons for CG to wait. "Precedent" maybe used to mean something to them, but in the last couple of years they haven't cared very much for it.

Also, did they even specifically say they would leave a TM loop DC? Or is it like the 90 day Legendary cadence that we all made up in our heads?