Biggs datacron

Another side note, I stopped playing for a year as a result of datacrons last year, this may well be the thing that stops me doing it again this year. Moves like this unincentivse people from spending money on your game or even playing it at all. This game is all about long graft so you HAVE to reward people for it to keep your players happy. Otherwise they might stop spending or leave. @CG_Tusken_Meathead

"Ultra;c-2462834" 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 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

Yeah, this is what confuses me a bit. Why are they 'fixing' undesired interactions in datacrons when the whole point of them was to be a temporary boost? I was pretty close to adding more relics to Biggs just for this - I have the datacron but my Biggs is R3. I imagine a fair number of people bumped him to R5 specifically for this (I know for sure at least one of my guild mates did).

At the end of the day, it doesn't really matter to me what they do with it - it's just not that serious to me - but I can't help but feel like this pulls the rug out from under at least SOME players. Who knows how many resources people expended for this specific interaction?

I don't often cry "make good!" but this does strike me as one of those cases where it's warranted - in particular because (anecdotally) more and more people are giving in and buying into datacrons - anything that discourages that trend would seem ill-advised. I'm honestly not sure what harm could come of reimbursing people for their investment after changing the rules on them. The net result is that those players have what? one more datacron? How would that not be a good thing both for the players and for the game as a whole?

I have biggs cron but he is still r3. Good i didnt care...

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

That's why IP are awful and I can't trust CG/EA anymore (or almost every games as a service), their actions are not always consistent and since they own everything you just have to accept them or leave.
If they changed their mind, at least they should provide an explanation.

If this wasn't for SW, this game would be dead long time ago ... yeah , I'm looking at you LoTR: HOME !

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

"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?

"Gawejn;c-2462851" wrote:
I have biggs cron but he is still r3. Good i didnt care...

Hooray

"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?

Only one currently available datacron makes use of that modifier and that is the Biggs level 9. They could have easily waited 2 months to include the change for the next datacron set.

"wharp;c-2462854" wrote:
That's why IP are awful and I can't trust CG/EA anymore (or almost every games as a service), their actions are not always consistent and since they own everything you just have to accept them or leave.
If they changed their mind, at least they should provide an explanation.

If this wasn't for SW, this game would be dead long time ago ... yeah , I'm looking at you LoTR: HOME !

CG doesn't communicate the way we want. They never have, and they never will.

Also, way to cherry pick an example. Before this game was Heroes of Dragon Age. It ran successfully for years before GOH and continued to run until a couple years ago.