Two of my Fleet's Starbase projects have identical Duty Officer inputs. Note that these projects were slotted a very long time ago. I'm not sure if this is a bug or intentional.
That's not a bug. Fleet projects used to have separate inputs for duty officers from different departments: tactical and security were separate; engineering and operations were separate; science and medical were separate. The problem was that there is an imbalance in the availability of doffs from different departments. For example, science is much more common than medical. After many complaints, Cryptic decided to change fleet projects to allow two types of doffs for the same input. For example, inputs that used allow only engineering doffs now allow both engineering and operations doffs, and inputs that used to allow only operations doffs now allow both engineering and operations doffs.
That's not a bug. Fleet projects used to have separate inputs for duty officers from different departments: tactical and security were separate; engineering and operations were separate; science and medical were separate. The problem was that there is an imbalance in the availability of doffs from different departments. For example, science is much more common than medical. After many complaints, Cryptic decided to change fleet projects to allow two types of doffs for the same input. For example, inputs that used allow only engineering doffs now allow both engineering and operations doffs, and inputs that used to allow only operations doffs now allow both engineering and operations doffs.
Then why did they not merge the projects? I don't imagine it'd be hard.
Can you "retire" a project (no longer slottable) and offer a new version?
That would require rebuilding most of the projects in the main base just to make things look slightly better. There are other quality of life fixes that require a lot less time to implement and actually make a difference to players like replacing the input for shield gens with one that costs more and decreasing the amount of commodities that need to be put in so we don't have to spend more time giving our EC to the fleet than it took us to earn them.
Some of these range from overkill like "Reinforce Local Systems IV" that requires 10,000 shield gens to absolutely ridiculous like "Upgrade Communications Array V" that requires 55,000 shield gens and 95,000 comm arrays when they could have used a more expensive input that requires 1/6th less time at a vendor. Big fleets run this stuff over so fast the thematic benefits are lost on them and small fleets spend so much time on it that they resent it so no one is actually made happy by this choice of fleet project input.
So, it is a bug, but I still have to fill it for now. Great. Well, thank you for telling me at least.
It's not so much a bug as a limitation of the code from when they changed the input requirements to not be restricted to specific departments. Either way, it doesn't really matter. If they combined them, then the total would still be the same so you wouldn't be saving on DOFFs.
Join date is wrong, I've actually been around since STO Beta.
True alters don't have a "main". Account wide unlocks for all unique event rewards!!
Comments
Then why did they not merge the projects? I don't imagine it'd be hard.
Data issue. If anyone had a project in progress and we deleted one of the fields by merging it with another field, Bad Things Would Happen.
That would require rebuilding most of the projects in the main base just to make things look slightly better. There are other quality of life fixes that require a lot less time to implement and actually make a difference to players like replacing the input for shield gens with one that costs more and decreasing the amount of commodities that need to be put in so we don't have to spend more time giving our EC to the fleet than it took us to earn them.
Some of these range from overkill like "Reinforce Local Systems IV" that requires 10,000 shield gens to absolutely ridiculous like "Upgrade Communications Array V" that requires 55,000 shield gens and 95,000 comm arrays when they could have used a more expensive input that requires 1/6th less time at a vendor. Big fleets run this stuff over so fast the thematic benefits are lost on them and small fleets spend so much time on it that they resent it so no one is actually made happy by this choice of fleet project input.
So, it is a bug, but I still have to fill it for now. Great. Well, thank you for telling me at least.
It's not so much a bug as a limitation of the code from when they changed the input requirements to not be restricted to specific departments. Either way, it doesn't really matter. If they combined them, then the total would still be the same so you wouldn't be saving on DOFFs.