Jump to content

Persisting Companion Bugs After 5.10.2


Kataret

Recommended Posts

Greetings community!

 

Since the launch of 5.10, a fair amount of companions bugs have come and gone, and by this time most of them have been complete. My old list here is rather obsolete, but there are still a few companion bugs that persist and should be remembered so that they are eventually fixed. I don't know which bugs still exist, but please comment below if I missed any that persist.

 

Thanks y'all, and here's to bug-free companions!

 

ALL COMPANIONS

  • Companions are still becoming inactive in combat. This occurs if the companion is more than 30 meters away from their target when combat begins.

 

Theron Shan

  • On characters that skip to Ossus, it's possible that Theron Shan will not show up in their Companion & Contact lists, thus making him unavailable for story missions where he is meant to act as a companion. This seems to have no effect on story cutscenes. This issue was noted to have occurred on a Trooper.

 

Paxton Rall

  • Paxton doesn't have anything to say when you right-click on him as your active companion.
  • Gaining Paxton from the holocom makes his Alliance Alert unavailable.
  • Paxton's character sheet offers empty gear slots for the head, chest, wrists, waist, hands, legs, feet, and an offhand. Equipping anything in these slots has no effect on Paxton's appearance. In addition, he cannot wield an offhand blaster, despite there being a slot for one.

 

Darth Hexid

  • Getting Darth Hexid from the holocom makes her Alliance Alert unavailable.
  • Every time you speak to Darth Hexid in the Alliance base, she will treat it as the first time you've ever spoken to her, as opposed to Ranos and Paxton who will recognize you if you've already completed their recruitment missions.

 

Nico Okarr

  • Nico Okarr does not have gear slots to customize his gear.

 

Malavai Quinn

  • Warriors who reunite with Quinn on Iokath run into a problem. When trying to place a decoration of Quinn in their stronghold, the Quinn who appears is a hologram and wears only underwear. Now that's just crude.
  • Sith Warriors who align with the Republic on Iokath and recruit Quinn run into an issue. When starting Jedi Under Siege, these players lose access to Quinn and cannot summon him from the Companion Odessen Terminal.
  • There continues to be confusion as to whether or not Quinn should be obtainable (via the terminal) for characters who sided with the Republic on Iokath. In these cases, Quinn was retrieved from the terminal only to be lost upon starting Ossus. It is unclear whether the bug is the initial retrieval from the terminal, or the loss as a result of Ossus' story.

 

Elara Dorne

  • There continues to be confusion as to whether or not Dorne should be obtainable (via the terminal) for characters who sided with the Empire on Iokath. In these cases, Dorne was retrieved from the terminal only to be lost upon starting Ossus. It is unclear whether the bug is the initial retrieval from the terminal, or the loss as a result of Ossus' story.

 

Jace Malcom/Empress Acina

  • Although it isn't causing any problems for story missions, there are still some players who have Malcom's and Acina's statuses incorrect.

Edited by Kataret
Link to comment
Share on other sites

I still have Malcom and Acina both listed as dead on my Imp's who went Republic on Iokath.

 

Also ran into a new companion problem. After finishing the class story on my new Trooper, he then skipped straight to Ossus and Theron is missing from his contact list. He shows at the Odessan base and showed in the Jedi Under Siege cutscene but he's not in my contacts list (and as such I can't get the Alliance Alert for M1-4X. All other alliance alerts that were still available from the Alliance specialists are there.) Theron's not on the terminal either, it's like skipping just made him fall into the void.

 

Tried running various KOTFE/KOTET chapters (like chapter 9 of KOTFE where he first returns) but the ones he should show up in, like the Kaliyo chapter or the Dragon's Maw chapter, he doesn't, thus making the chapters unplayable.

 

Not a major problem right now but if future story requires me to use him or contact him, I'm stuffed. :o

Link to comment
Share on other sites

If you align with the Republic on Iokath and retrieve Quinn from the terminal, when you start JUS he becomes inactive. Ditto Dorne if you align with the Imperials on Iokath and retrieve her from the terminal, she well become inactive when you start JUS.

 

Also with Quinn, if you are a Warrior who sides with the Republic, but keep Quinn, he was also become inactive when you start JUS, even if you married him.

Link to comment
Share on other sites

If you align with the Republic on Iokath and retrieve Quinn from the terminal, when you start JUS he becomes inactive. Ditto Dorne if you align with the Imperials on Iokath and retrieve her from the terminal, she well become inactive when you start JUS.

 

Also with Quinn, if you are a Warrior who sides with the Republic, but keep Quinn, he was also become inactive when you start JUS, even if you married him.

 

I'm fairly certain the first paragraph isn't a bug. Quinn and Dorne were never meant to be terminal-available if you didn't align with their respective factions. When you start Ossus, it seems the game tries to correct this issue, and removes Quinn and Dorne from characters where they don't belong. It's probably a bug that you can get them from the terminal at all.

 

But the second paragraph definitely seems like a bug. Quinn can legitimately be recruited by a Republic-aligned Sith Warrior. However, the game is likely failing to recognize this, and instead sees the Warrior as another Republic-aligned character that shouldn't have access to Quinn. The result is that Quinn is removed from those Warriors even though they naturally recruited him in the story.

 

Ranged companions staying too far back and not healing is still a major issue.

 

This is still an issue? I was under the impression it had been fixed. Oh well :confused:

Edited by Kataret
Link to comment
Share on other sites

I'm fairly certain the first paragraph isn't a bug. Quinn and Dorne were never meant to be terminal-available if you didn't align with their respective factions. When you start Ossus, it seems the game tries to correct this issue, and removes Quinn and Dorne from characters where they don't belong. It's probably a bug that you can get them from the terminal at all.

 

I have a lot of trouble believing Quinn and Dorne being on the companion locator terminal is a bug. (I kind of thought that was the whole point of the terminal.) That would be a very bizarre bug from any kind of programming standpoint. That and Iokath was 2 years ago, so for 2 years players have been happily retrieving them from the terminal without Bioware ever saying a word. Whereas we were directly told that JUS was categorically not supposed to remove any companions from us.

 

So if it genuinely is a totally bizarre and unprecedented bug, then that is a severe persisting companion bug that should be acknowledged and fixed immediately so players don't continue to lose gear and high influence companions out of ignorance. Or it should be treated like the Marr/Acina/HK-55 bug, where it was obviously not intended for them to be retained, and be fixed in favor of the players who invested in those companions.

 

This is still an issue? I was under the impression it had been fixed. Oh well :confused:

 

Nope, not fixed at all. Not even sure it's been acknowledged yet.

Edited by Damask_Rose
Link to comment
Share on other sites

I have a lot of trouble believing Quinn and Dorne being on the companion locator terminal is a bug.

 

You might be right. I had been basing my information off this post, which contains a response from customer service. But customer service has been wrong before, so the information in the post could be wrong.

Link to comment
Share on other sites

Nope, not fixed at all. Not even sure it's been acknowledged yet.

 

On March 11th Musco responded to this post asking about the ranged comp issue with the below response. Nothing since that I've seen.

 

Originally Posted by Setokai

Any chance the problem of companions not attacking a target over 30 meters away being addressed in that patch?

 

This will not be fixed in this patch. We definitely understand this is a big issue, on our side it is also a pretty large undertaking to resolve. We have people actively working on the fix but I would not expect it super soon. I do not believe it is in 5.10.2 (our next major patch) but it is in the works to hopefully come thereafter.

 

I will provide more details as I get them.

 

-eric

Link to comment
Share on other sites

You might be right. I had been basing my information off this post, which contains a response from customer service. But customer service has been wrong before, so the information in the post could be wrong.

 

That was my first response from CS. I wish I'd kept the second one where they said I shouldn't have lost Quinn and that they were happy to restore him to me. Every time I've contacted them over this issue they've been wildly all over the place in their responses which leads me to believe they have no clue how anything is supposed to work, what is intentional and what is a bug and what they can and cannot fix.

 

This is no bug, this is intended. Not all companions have this Option.

 

You are right, it's not a bug. It's just an ongoing, irritating as hell issue. For me, that's worse. That means they made the deliberate choice to upgrade the female companions, but not the male ones.

Link to comment
Share on other sites

You are right, it's not a bug. It's just an ongoing, irritating as hell issue. For me, that's worse. That means they made the deliberate choice to upgrade the female companions, but not the male ones.

 

That is an unfortunate oversight. The Devs did give gear slots to Theron and Koth when they were adjusting companions, so I don't think it's necessarily a deliberate bias against males. I guess Nico was just forgotten among more important companions like Lana, Senya, and Theron.

 

Though Arcann is also missing this options, so you never know...:eek:

Link to comment
Share on other sites

I got a reply back from my ticket about my Trooper missing Theron. They told me to replay Chapter IX and that Theron should then be summonable on the Odessan terminal after. He was not. :rolleyes: At this point I'm half tempted to just use a token, but the whole point of skipping to Ossus on this Trooper was so I didn't have to play it all for a second time on a Trooper. :(
Link to comment
Share on other sites

That is an unfortunate oversight. The Devs did give gear slots to Theron and Koth when they were adjusting companions, so I don't think it's necessarily a deliberate bias against males. I guess Nico was just forgotten among more important companions like Lana, Senya, and Theron.

 

Though Arcann is also missing this options, so you never know...:eek:

 

I should have been more clear. I was only talking about the 5 "reward" companions, not the main story companions. All of the main story companions got upgraded, except Arcann who has the cybernetic arm. I assume it was deemed too time intensive/costly to rework him with the arm. So all three female "reward" companions got upgraded (Hexid, Ranos & Shae), but neither of the two male "reward" companions did (Nico & Paxton).

Edited by Damask_Rose
Link to comment
Share on other sites

the theron shan bug is also happening to aric jorgan, coincidentally its also happening on my trooper after ossus. he appears in chapter 11 with all of the stuff i gave him, but when i remove the quest / complete it he completely vanishes from my companions & contacts list. he isnt there, he gets deleted. he also doesnt show any outfit or customization when in a stronghold whilst im on that particular character.
Link to comment
Share on other sites

Just wanted to say, after submitting a second ticket to customer service, I finally had a rep message me today (I was in the middle of a KOTET chapter on another character when they wanted to check out my Theron issue) so I logged out and later got an email later, saying they'd granted my Trooper, Theron and to check all was okay. Logged in and checked, and can happily report that my Trooper who had skipped to Ossus and lost Theron to the void, has now had him returned to him. :)
Link to comment
Share on other sites

×
×
  • Create New...