I was not able to change my ship's bridge on any Fed, KDF, or Romulan character. It does not matter if I include any additional ship changes or not, the bridge change simply reverts upon application, and additional EC charges that would have been taken for the bridge and layout change are not deducted. It is not ship, character, or account specific, as all ships, all characters, and all accounts, are identically affected.
This renders it impossible to use the bridges that I have paid for, and this is very uncool.
I have an update on this bug: Apparently, it IS possible to change it at OTHER tailors, but NOT at your starbase tailor.
So something is wrong with the Starbase Ship Tailor.
This is not very helpful to units I have deployed at places with no ship tailor that have had their bridges forcibly changed to that Origin thing, which is a navigational mess.
I customized a ship at my fleet starbase a while back and it worked fine.
However, the starbase tailor said that additional tiers needed to be unlocked before I could use it and clicking the back button in the window switched it to the option to customize my ships.
Kinda like the exchange console at my KDF embassy. When right in front of it I see 2 buttons: 1 that says the exchange service is not available and 1 that allows me to access it and it works fine. I reported this bug a while back on the forums, with screenshots, and it's still not fixed.
Comments
So something is wrong with the Starbase Ship Tailor.
This is not very helpful to units I have deployed at places with no ship tailor that have had their bridges forcibly changed to that Origin thing, which is a navigational mess.
However, the starbase tailor said that additional tiers needed to be unlocked before I could use it and clicking the back button in the window switched it to the option to customize my ships.
Kinda like the exchange console at my KDF embassy. When right in front of it I see 2 buttons: 1 that says the exchange service is not available and 1 that allows me to access it and it works fine. I reported this bug a while back on the forums, with screenshots, and it's still not fixed.