I have an odd bug with the space skill "gravity-well-1". It literally changes itself into the space skill "evasive maneuvers-3" when adding it to the skills-tray. Here are the details:
(1) When trying to set the skill "gravity-well-(rank 1)" in the space-skills-tray (click+drag the ability from the skills-list-(P) into the tray) it literally changes this skill + the icon + the description of this skill (if you hover over the icon in the tray) into a completely different skill "evasive maneuvers" instead.
***NOTE: I am NOT accidentally selecting normal "evasive maneuvers" skill from skills-list-(P). Also "gravity-well-(rank 1)" in the skills-list-(P) displays the correct icon + information, before trying to add it to the tray.
(2) This bug occurs specifically when using it on the Science-Jem'Hadar-Vanguard bridge officer + on ANY ship (with relevant science-seat/slots) + on ANY lieutenant-commander science/universal slot it seems. I have not encountered this bug on any other bridge officer so far I think.
***NOTE: I definitely have "gravity-well-(rank 1)" unlocked + selected for this bridge officers rank + seat/slot (I have not accidentally selected the wrong skill or something). Also I setup all the skills in a space-zone, rather than ground zone (in case the transfer from ground to space might cause a memory bug and lose the saved skills).
(3) This bug seems to ONLY OCCUR on my new (KDF)-recruiter character/toon (called "Aved") - I have checked on several other characters I have (both federation and KDF aligned characters), and the bug for this specific bridge-officer does not seem to occur anywhere else.
(4) Other than the above mentioned icon/text change in the space-skills-tray, I get no other kind of errors or error messages that I can see. In fact, when this skill changes itself into "evasive maneuvers" in the skills-tray, the skill works exactly as if it were regular "evasive maneuvers".
The only other information I can add really, is this new (KDF)-recruiter character I have is at maximum-rank - if that is at all relevant to this bug.
I've put in a bug report ticket about this, and it is being looked at.
0