The fleet is unable to advance in Fleet Starbase projects upgrades due to a BUG that has yet to be addressed. The fleet starbase has been stagnate for a few months now due to the following:
1) when players BUY common bridge officers at the barracks (KDF Side) with Dilithium, the project does not read them, or recognize them, hence they are not accepted by the project.
Here is a screenshot of the project in question:
Click Link -->
Project that is running that cannot be completed
As you can see by the link, the project requires 45 Common Bridge Officers as a donation, that is 15 of each profession.
15
Tact, 15
Eng, and 15
sci
Unfortunately; this bug is being taken advantage of by the community, since players buy the defunct common BO's from the barracks and then post them on the exchange for over 250K.
The introduction of the tutorials on both KDF and Fed sides have replaced the earlier beginner missions that use to grant common bridge officers as a reward, this is no longer the case.
There is NO current episode mission that rewards common bridge officers. This MAIN Fleet Upgrade project cannot be completed.
It will be helpful if I can get a response from one of the Devs to this post, since I would like to know what is the underlying issue with this bug. That way I can communicate this to my Fleet members.
Thanks
Comments
It is not the project itself, but the common bridge officers requisition. This effects fleets that have been created after the implementation of the KDF tutorial as well as Federation tutorial.
It may actually be linked to those addons. However; ever since they introduced LoR, the game has been plagued with more severe BUGS.
I might be wrong, but I am hoping for a dev response in regards to this one particular issue. Simply put, there are no common BOs to satisfy the requirement of the project.
and yes:
SMALL FLEETS BEWARE - for both KDF and Fed
free jkname
Get the Forums Enhancement Extension!
The stuff brought from the dil store is bound that's why
We had to buy from exchange to do ours
I don't think that is the case - I am sure the op has tried to use exchange bought boffs
This is a bug that returned.