I've tracked down the issue at hand. It stems from not all Bridge Officers sharing the same defining config files.
So, while these projects are set up to accept generic Boffs of the associated types, those Boffs are only currently obtained thru receiving a "Failure" outcome on Duty Officer assignments that recruit that species of Boff. The ones purchased at stores, or received from mission completion, are different config files, even though they share the same Display names. Therefore they cannot be used for these projects at this time.
We'll be updating the Projects to accept a wider range of Bridge Officers (hopefully encompassing all possibilities), and should have that fix in next week's patch.
Fleet Starbase Personnel projects should now properly accept Bridge Officer donations.
Which WASN'T and ISN'T the case. It's annoying that after hearing the fix will be in this next patch, we here nothing further on the status of something Cryptic QA didn't test properly in the first place; yet STILL claimed it was working in official patch notes of 11/21/12.
If you can't fix it, either allow it to complete for the unfortunate Fleets who were gullible enough to think something in STO's official Holodeck patch notes was accurate; OR allow us to unslot the project so it's not blocking future Fleet Starbase upgrades. (or at the very least give us some further status on where a possible fix is at.)
Formerly known as Armsman from June 2008 to June 20, 2012
PWE Drone says, "Your STO community as you have known it is ended...Display names are irrelevant...Any further sense of community is irrelevant...Resistance is futile...You will be assimilated..."
Updated the level range of PvE private queue maps.
This affects only those PvE queue maps for which the level can be adjusted.
The level of a queue map must be within two of the queue's creator.
Players that are more than two levels above the map's level cannot join.
For example, if a level 10 player creates a private queue, he can set it to levels 8 through 12.
Players level 10 through 14 would be able to join this example queue map.
Damn, I guess that means no more running Starbase 24 in my Fleet Patrol Escort with level 6 enemies ...now that was that fun. Quantum Torp Spread III not only blew up the Neg'Vars, but also everything around them. It was too good to last I suppose...all that dilithium in about 5 minutes.
Last edited by majortiraomega; 11-29-2012 at 12:14 AM.
All Gorn ship descriptions in the ship store now accurately display +15 Auxiliary power in the ship store.
so about the gorn ship, why does it have a lower shield mod then fed sci ships? and since it does, why doesn't it have more hull hitpoints, a faster turn rate, a more interesting station setup, anything to make up for that disadvantage?
the gorn ship is a stat clone of the deep space sci ship, except it has a 1.2 shield mod instead of 1.3. both the vulcan and nebula have higher hull hit points, and keep their 1.3 shield mod. i cant find an ounce of fairness in any of this, its no wonder n oone uses the gorn ship.
oh but it has the repair drone console, vulnerable pets with a long cooldown. the fleet version wont even come with the console, you will need the c store version to get it. its been a long time since a console like that has been a reason to give a ship a stat disadvantage, the fleet version of this ship should have at least the same shield hitpoints as a fleet deep space sci.
or you could do something really cool, and give it a vesta station setup, you would sell plenty of those ships if you did that! did you lose money on this ship and other kdf ships? well thats because they weren't great, or they were low tier! people buy end game ships, only RP carebears are gonna buy a lot of low tier fed ships.
This is good and all but what about Fleet project fixes thought the been in one of these patches or did i miss it where you can put all common BOFFS in the project station personale , cause right now only common boffs that you get from failing a doff mission where you get a boff in ,