mudekk Posted July 5, 2013 Share Posted July 5, 2013 (edited) I recently reported a bug for Area+2 A City Held Hostage on Makeb. I am not able to successfully progress through the mission. When I opened a ticket to report the problem, SWTOR's reply said, "We are sorry that you have encountered an issue with your mission, however please be advised that we currently only offer support for class story missions." I am disappointed is SWTOR's lack of customer service and apparent disinterest in improving the game and providing players with a satisfactory gaming experience. I immediately cancelled my subscription; I'll play something else. I am the one playing and paying for the game; my opinion matters. If the developers can't understand that, then that's their problem. This ain't the only pc game out there. Edited July 5, 2013 by mudekk Link to comment Share on other sites More sharing options...
Kain_Turinbar Posted January 13, 2014 Share Posted January 13, 2014 Found this bug today 6 months after your post. Can't believe this is still in the game. Link to comment Share on other sites More sharing options...
CrazyMcGee Posted January 13, 2014 Share Posted January 13, 2014 What's the bug? I've done that mission loads of times. Link to comment Share on other sites More sharing options...
JamieKirby Posted January 13, 2014 Share Posted January 13, 2014 There are loads of bugs that have never been fixed, they tend to only fix bugs that prevent you from progressing in your class story, unless the bug has a workaround, like the crashing on the Black Talon / Esseles flashpoints, the workaround allows it to work 100% with no crashes, so bioware can't be asked to fix it. Link to comment Share on other sites More sharing options...
Kain_Turinbar Posted January 13, 2014 Share Posted January 13, 2014 What's the bug? I've done that mission loads of times. When you get to the part where you call in the airstrike with that field command terminal it won't let you interact with it. It keeps giving you the "You can'd do this at this time" message and you're stuck. Some say switching instances works but I tried 3 different instances last night then abandoned the quest and moved on. Link to comment Share on other sites More sharing options...
MichelBois Posted July 11, 2014 Share Posted July 11, 2014 When you get to the part where you call in the airstrike with that field command terminal it won't let you interact with it. It keeps giving you the "You can'd do this at this time" message and you're stuck. Some say switching instances works but I tried 3 different instances last night then abandoned the quest and moved on. I have the same prblem with the console, glad I am not the only one. Is there another solution? Link to comment Share on other sites More sharing options...
EnkiduNineEight Posted July 11, 2014 Share Posted July 11, 2014 I would have tried resetting the quest. I never have run into this specific bug so I don't know if my suggestion would work. Link to comment Share on other sites More sharing options...
Anaesha Posted July 11, 2014 Share Posted July 11, 2014 I would have tried resetting the quest. I never have run into this specific bug so I don't know if my suggestion would work. It's probably a bug like the Black Talon/Esseless crashing at the end of the FP which only seemed to happen to certain players. Those that say they will never fix it. They fixed the BT/Esseles bug they will fix this eventually you just need to have patience. Link to comment Share on other sites More sharing options...
EnkiduNineEight Posted July 11, 2014 Share Posted July 11, 2014 It's probably a bug like the Black Talon/Esseless crashing at the end of the FP which only seemed to happen to certain players. Those that say they will never fix it. They fixed the BT/Esseles bug they will fix this eventually you just need to have patience. That bug is a graphical glitch that caused some videocards to wig out and crash when the hyperspace jump is made isn't it? This instead appears to be a triggering issue, where an interactable object is nt turned on due to a scripting glitch. I've found in those instances the best thing for me to do is just restart the quest (if I really want it done) and follow the instructions very carefully and let it show me the full cut screen and or wait for each notification of quest update in full before rushing to the next step. Link to comment Share on other sites More sharing options...
Heat-Wave Posted July 11, 2014 Share Posted July 11, 2014 Found this bug today 6 months after your post. Can't believe this is still in the game. Why can't you believe it? EA long ago clearly decided to not repair the many, many broken things in this game. A few things get fixed, such as the Hyperspace jump crash, but that likely got fixed only because so many new F2P players crashed there and gave up on the game being new. The staff running this place now is likely quite small, they just don't have the time or resources to go back and clean up the thousands of little bugs left over. Link to comment Share on other sites More sharing options...
Recommended Posts