Dejawesp said:
Vrach said:
First off, that's not Sith, that's you. So if anyone's being stupid, it's you for making the choice.
But its not a choice. If a player wants a dark aligned character with the accompanying equipment then they must choose this course of action regardless.
Yeah, it's a choice, there's light side equipment as well, not to mention the countless unaligned gear. Choice having consequences doesn't not make it a choice, quite the contrary actually. But if your argument is "well, one choice yields ridiculously better results than the other (in terms of gameplay)", well then, that's just bollox, it's simply not true.
Not to mention, choosing that option doesn't instantly make you a light side character, you can make other dark side decisions to counter it. Even if, hypothetically, you're a goody two shoes who chooses a light side option every single time, you can take Diplomacy and run enough dark side missions to sway your alignment for gameplay purposes, if you seriously think you NEED that gear and have no option (which is really, just silly).
I for one don't whore my decisions for points, I choose based on what I think is right for my character. And, for what it's worth, I cut that captain down without a second thought, because that's what my Sith character is like.
Dejawesp said:
Vrach said:
At best you can call that Dark Side Sith stupid, but that's not it either, at least not for your example. You execute the captain for disobeying a direct order in combat, during a (granted, cold, but still a) war. And the order was "assault", which I'm actually mauling over whether it counts as desertion (the punishment for which is death, even in today's RL military I believe).
Even if the captain was to be executed eventually. Doing it right in the middle of a critical mission where you need his ship is stupid. Criminally stupid. His fate should be decided at a better time.
You don't need him, you need his ship. His ship is not attached to him in any way, nor is he the only or even the most competent person to command it.
You're disposing of an incompetent, insolent leader in a manner that both transfers the command of the vessel to you (something which you're fully capable of handling) and inspires your surrounding troops not to question your orders (nor the orders of their superiors in the future) further - a message that will be sent even further than that vessel by soldiers talking, insuring obedience in your army. No, stupid is a very far fetching word for that decision.
Let's try this another way, have you ever played the Total War series? Well, if you have, you'll know that there are military situations where you need to send your army/units on what's essentially a suicide mission/battle. But see, thanks to moral, they're not gonna be happy about that and are gonna be running away at some point when they realise they don't have a shot. Now, as a leader, you know, that for the sake of the bigger picture, for the sake of your empire, you need that army to do it's best, fight tooth and nail to the last man and listen to your every command. But that doesn't come naturally to armies. What the Sith Empire does, the way it treats its military, it results in a very determined set of troops. Because they know, if they back down from a fight, even if it's a suicide mission, they'll be cut down by their own superiors.
You remember the Russian Red Army? You remember the "not a step backward" motto? You remember the officers ordering deserters shot in the back during the actual battle? We're talking about one of the most powerful and fearsome armies in the world of the time. That's what the Sith Empire is like, only, I would say, with a lot more finesse, doing those things out of discipline, instead of desperation.
Dejawesp said:
Vrach said:
Second, you don't know the lieutenant is inexperienced at the time, and hell, you didn't know the captain WAS experienced.
Third, this is how the Empire operates and it's how a lot of successful armies operate. Insubordination (on this level) means death, which leads to greater efficiency. Now, you may trust your subordinates to make the right calls at the right time, but that's just not how the Empire works, it's built on a strict hierarchy.
He is the captain of an entire warship. It is very likely that he is at this point an experienced captain and he is certainly more experienced than his subordinates. Hence why they are his subordinates.
The Sith teach to never waste a resource and for the duration of the mission the captain of the ship is an important resource. Killing him in the middle of the mission to "make a point" makes about as much sense as a tank gunner shooting the driver in the middle of a battle for insubordination and then complaining about the tank stopping.
The choice to kill the Captain is in fact so stupid that the game has to alter the republics attack to compensate for it.
If you let the captain live the republic launches sabotage droids and boarded vessels against the Black Talon. The captain evades the droids and the players deal with the boarding party. If you kill the captain then the boarding party mysteriously vanish and the players are left to handle the droids.
And how does killing the General amount of "personal benefit"? The Empire wants the general alive but killing him is acceptable as a last resort. The player does capture him alive but then kill him in custody and for what? Just for the fun of it? That is stupid evil. Its evil for its own sake and that is poor writing
Again, you're taking command yourself for the time being, not giving it to the lieutenant.
You're overestimating the captain's worth and your analogy makes him out to be a pilot, not a captain. The captain is merely a figurehead that gives orders to the others on his warship. You're capable of this task yourself and he clearly isn't - so you cut him down, because his own worth is less than the worth of showing your troops the cost of insubordination. Darth Vader did this many times in the movies and that wasn't even out of insubordination, but simply a price for failure, which is far more ludicrous.
I can't respond to the game altering thing because I haven't played the Flashpoint enough times to try both options, but either way, the game does it because it wants the situation to be different, not because (and I want you to read this out loud, so you can hear how stupid it is) your group can't handle the boarding party because an NPC is dead.
The general's life is irrelevant. I just went back through the dialogue to ensure that I'm not talking out of my arse and the situation is following:
1)The general is not a resource. He is someone who is supposed to have intel on Empire military secrets.
He has nothing to benefit the Empire, only a way to harm it. Killing him ensures he never escapes and/or gives that intel away. Letting him live is what's stupid, the only reason for it being ethics, not logic and the Empire does not have a set of ethics that would make that an issue.
2) "The Empire wants him alive" - now that's just straight bullshit. Grand Moff Kilran himself tells you plainly that he is to be captured or killed.