So is this weapon supposed to drain the all power from the planet merely by existing, or does it drain it only once it is fired upon the enemy fleet? The latter is what I understood to be the case and would make the most sense, but dialogue with Carsiri and Madine suggests that Balmorra will pay that price no matter what, even if the Republic would simply possess it as a deterrent against future Empire invasions. Can anyone shed some light on this?

It was weird.

Best way to avoid the bug in my experience is to play all the chapters up to the the lock-in point on Odessen in a row and use all the flirt options.

I'm a big fan of the Emperor as a character, but I think they should have just left him alone after KOTET finale. And bringing back all those dead characters like Revan, The Exile and Darth Marr just felt cringy to me.

Yeah it was terrible, tbh. Mobs take wayy too long to kill on SM. Had to call it quits when I exited the dialogue with the second boss and couldn't initiate it again.

I also did not get this issue while siding with the Republic on Iokath. Probably because the bug was already fixed by the time I completed it.

Oh. Well that's just great...

I thought it was weird that you just zoned in with no cutscene or dialogue. Hope this gets fixed ASAP.

It seems that the fix for this is imperfect. I've completed the bonus series for Tatooine -- including this particular quest -- days ago with the Light side option and although I have not received a Dark side mail I have not received the correct Light side mail, either. So in short, you won't get any mail, either the Light or Dark side version, if you complete Militia's Trial with the Light side option.

I think I noticed the same issue in the KOTFE chapter Visions In The Dark. The items inside and just outside Satele's ship didn't show any info when hovering over them with the mouse.

Can you confirm that this is being tracked and will be fixed, BW?

Are you aware of this, BW? I'd like to see this fixed.

It's been months now since your post and years since this bug was originally reported. Can we get some answers already as to what the status of the fix is?

Can someone confirm that this is indeed fixed now?