> > > Hi Captains! The team is investigating an issue where some players may be stuck on a loading screen. Thanks for your patience! < < <
We are aware there is a queue to log in at this time. We are working to get you in-game as soon as possible.
UPDATE!We're aware of a Skill Points issue that some Romulan Liberated Borg captains may be experiencing, as well as players not being able to delete mail, and are working towards a resolution.
Jolan tru Captain!
Welcome to Legacy of Romulus!
If you have purchased a Legacy or Starter Pack, please see this thread for instructions on how to claim your items in-game. (Please see the yellow text in the linked thread for instructions on creating a Reman.) (Not seeing your pack in-game? Please see the lime-green text in the linked thread above for information.)
If you have additional questions about the Legacy or Starter pack, please read this FAQ.
Thanks SO MUCH for all your support, and we'll see you in-game!
- The Star Trek Online Team
***Resolved Issues***
"Login failed for unknown reason" error
Missing additional character slot for current/ lapsed Gold Members
Issue:
The Omega personal shield generator is supposed to proc an expose on the damage owner when receiving all damage. It currently procs an expose on the shield's wearer, not the damage owner, when receiving all damage.
Duplication:
Put on the Omega shield. Have someone shoot at you, primary fire only. Observer that exposes are procced on yourself (when none should be). Observe that no exposes are procced on the damage owner.
Notes:
We also tested the standard means of putting exposes on targets. These are working as intended. We tested with no omega shield, and received no exposes when receiving damage from non-expose attacks. The problem is isolated to the omega shield.
I did some testing of my own. I recorded two videos to demonstrate the bug in action:
Omega Shield mk XI - Bugged Expose Proc: Test 1 shows the bugged shield and its effects. Primary fire from a sniper rifle only exposed the target. The damage owner was never exposed, which would be the case if this shield was working properly.
Omega Shield mk XI - Bugged Expose Proc: Test 2 Shows what happens with a standard shield; nothing, just as it should be. This proves that the weapons themselves are not bugged, but rather the shield.
I've yet to suffer from it in PvP but this has big consequences for users of the Omega Force ground set.
Joined: January 2010
Fanfiction! ZOMG! Read it now!
kate-wintersbite.deviantart.com/art/0x01-Treachery-293641403
Note that since the Borg do not have Exploit attacks, you are still safe using the Omega shield in STFs.
Quoted from another post for reference. This is not what I'm experiencing in STFs.
I am getting exposed in STFs while shooting at Borg. I am not using the Omega shield, but my teammates are. So I suspect the proc works like this:
1 - when the proc activates, it applies a buff on you that will expose the next target that shoots at you. With the bug, I think this buff is being applied to the enemy instead of the shield owner.
2 - the first person who shoots at the buffed enemy (can be another teammate) will get exposed.
Unfortunately this suspicion doesn't match the tests in the OP, so it might be something else (like Borg actually having exposes). I have also noticed that I get exposed while doing absolutely nothing in STFs, but teammates are fighting. This is all very confusing.
I am pretty sure that the Borg use expose weapons (melee, spray fire on their guns) and expose powers (the green fuse armor equivalent is one, there may be others). This is most likely where your extra exposes are coming from, although there might be something to your hypothesis, too.
The Borg don't have any exploit abilities, though, so you don't need to worry about getting exposed.
... um. You meant exploit, not expose. *feels stupid*
To follow up on this and make this a bit less embarrassing (or more), I tested getting exposed while doing nothing in STFs while teammates with the Omega shield were fighting, and couldn't replicate it. So, uh... yeah. Carry on.