Wrong mission listed for build of 1* Isolinear Chips

Data1001

I don't farm these often, so I really didn't notice it outside of this event — but one of the recipes in this current Galaxy event requires 1* (Common) Isolinear Chips. And according to the wiki, the mission Arms Race, on Normal difficulty, is the best place to farm them.

However, in the listed possible missions when you go to farm that item, although Arms Race is listed twice, both are the Elite difficulty versions. The Elite difficulty has a lower drop rate than the Normal does. (And yes, I've confirmed that the Normal difficulty still drops this item. I have been getting 2 or 3 of them per single run of that space battle.)

I have also since confirmed that this is not just a problem with the build of that item in this Galaxy event, but that the same incorrect missions are coming up when building that item for a crew member.

There seem to be other cases like this that I've come across, though I haven't collected any details on them. However, it seems that this has probably been like this for a long time, and thus it should have been fixed by now.

Thanks in advance for passing this along to the team!

[DB-DO BETTER] [7TW] Captain plim123

This has been a bug for over a year. The most common offender is 1* Polyalloy from Behind Closed Doors.

Despite the fact that this has been:
- around since day 1
- raised as multiple tickets
- raised multiple times on both forums
- reduces the functionality of the game, especially in galaxy events
- robs unsuspecting players of chronitons (makes them farm from less efficient missions because they think the most efficient mission is not available)

...DB refuses to address it.

<Spock voice> There are two possibilities: they are unable to repond, they are unwilling to repond</Spock voice>

Data1001

Wow. This may have been fixed already. Or at least it was in a crew build. Only one version of Arms Race was listed (at least I didn't see another one right next to it) and it was the Normal one. Haven't had time to check if the recipes in the event are also updated, but I expect they would be.

[DB-DO BETTER] [7TW] Captain plim123

No, it comes and goes. Sometimes when you restart, it clears. Sometimes a restart causes the bug to appear. It really is random.

Data1001

[DB-DO BETTER] [7TW] Captain plim123 wrote: »

No, it comes and goes. Sometimes when you restart, it clears. Sometimes a restart causes the bug to appear. It really is random.

Oh it's not like that all the time? That's even weirder, then.

Data1001

You're right, plim. It's been bouncing back and forth between having one copy of that mission on Normal, and two copies of that mission on Elite.

DB, seriously, this is a crazy bug. Has anything been done to try to fix this, and the other bugs like it that plim mentioned above?

Data1001

Same problem with the build for 1* (common) Starfleet Uniform Pattern. 2 missions are shown for Cleansing Fire (alt. mission for By Hook or By Crook, depending on which faction victory you chose in that episode), but both are the Epic versions, when in fact the Elite version has the best drop rate — by a factor of nearly 2 to 1 — and yet the Elite version is not shown at all in the choices, forcing many players who don't know better to spend twice as many chronitons.

I'm going to keep adding to this, and anyone else who sees the same problem with other builds, please add your entry below. This is something that DB should have fixed long ago.

[RotP] Scoustar

Data1001 wrote: »

I'm going to keep adding to this, and anyone else who sees the same problem with other builds, please add your entry below. This is something that DB should have fixed long ago.

That they haven't yet means they can't. Unity is a <rudeword> to work with. It takes dedicated, talented, trained professionals an eternity just to find the bad coding.

Data1001

[RotP] Scoustar wrote: »

That they haven't yet means they can't. Unity is a <rudeword> to work with. It takes dedicated, talented, trained professionals an eternity just to find the bad coding.

I bow to your obviously far superior knowledge regarding the coding. However, I still have severe doubts that the reason any long-standing bug in the game hasn't yet been fixed is solely due to the perplexity of fixing said issue.