Biggs datacron

Correct me if Im wrong. Why the change CG just made on Biggs dc is considered a "bug fix"? Was it a bug that he gain TM in a loop? It feels more like a nerf than a bug fix to me.
Besides, there were lots of ways to prevent his infinite loop. For example, in a Leia squad a very fast C Rex or an Old Ben.
Many of us spend some relics on him to bump him from r3 to r5. Also crystals on rerolling the datacron. It doesnt feel fair.

Maybe not a bug fix, but unintended infinite loops tend to earn / deserve a nerf. Sure, it can be stopped by some teams, but not by many and not easily, and you can pick and choose that on Offense pretty well.

"iMalevolence;c-2462816" wrote:
They didn't get rid of DVs infinite loop during the Security Primer set. They set a precedent with inaction on the previous case. Players expected this cron to function as stated for the duration of the set and players have already invested resources into getting biggs crons that became (essentially) useless overnight.

This is a bad change that should not have gone through. Fix it for the next iteration of this modifier, but leave it alone mid set.

/edit Usually invalidating something that players have worked towards should be met with a make good. Run a script where everyone who has at least one Biggs cron gets something to make up for ruining all of those mats.

Absolutely agree. This is a nerf plain and simple, and a 'make good' should be issued. Materials for the current set, or just crystal equivalent would be fine.

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).

Yeah this is a crap change, CG. I hope all your pillows are warm on both sides until you walk it back!

"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 agree that infinite loops should be fixed whenever but now that you mention it, i do remember CG saying when datacrons were first introduced the benefits of DC were there that if there were some infinite loops combos, the good thing about DCs were they would eventually expire instead of them fixing them

and that CC is a good example

"Ultra;c-2462834" wrote:


i agree that infinite loops should be fixed whenever but now that you mention it, i do remember CG saying when datacrons were first introduced the benefits of DC were there that if there were some infinite loops combos, the good thing about DCs were they would eventually expire instead of them fixing them

and that CC is a good example

But why didn’t they at one time correct the datacron for Darth Vader, who could walk endlessly, destroying any legends?

Dear developers. Give us a counter-team against Leia's legend made up of characters not from Conquest and not new characters. Or return the old datacron to Biggs.
@CG_SBCrumb, @CG_Tusken_Meathead

This DC set has been available for a while now, almost at its midlife. I specifically upgraded a couple weeks ago Biggs from R3 to R5 and gave a zeta to MM lead (and not to mention, spent mats for the reroll) to use it in TW and GAC. There has been no communication about a possible change. This is a bad outlook for a resource management game, to live with the feeling that everything you invest that seems worth it might be changed and nerfed down the road. You could have just let it expire and change it in the future if you ever wanted it to come back. Now I feel that I am owed some recompensation or to have my zeta mats and relics back, because I would have never upgraded them if it wasn't for the DC (which again I repeat, it is not even that it was out for few days, you saw there was a problem and fixed it. It lasted for litterally two months!). I will open an EA ticket, unless some kind of "excuse us" is given. I know it may not be your decision, but this is not how you should handle matter in a game were resources are so fundamental.

@CG_Tusken_Meathead

Agreed, I specifically spent money to invest extra resources into this datacron set last conquest because it looked so good. Now with barely any use out of it the entire value of it has been taken away. To me this is as good as fraud - selling something deceitfully. We SHOULD be reimbursed for this