[aldo_14]

Originally posted by Goober5000
This could have been done with a source code hack also, presumably; but maybe that wasn't an option.

Not that Volition would ever do anything like that, of course...........

[TrashMan]

Originally posted by karajorma
I've said it before and I'll say it again. The Colossus was disabled. There was no way it could have escaped even if they had wanted to. Command orders them to get out and rather than remind them that he can't the Captain seizes his chance to get a posthumous medal and a bigger widows pension by appearing to have done a brave and noble thing.

Which makes even less sense. I DARE someone to try and disable the Colossus (or the Aquitane).
Both have several engines (and the Colossus has a kazillion HP).

[aldo_14]

As long as you keep up a concentrated attack, you can disable / disarm anything.  The Colossus had taken an absolute hammering by that point already; IIRC the fighterbay was destroyed or clogged by debris.

[FireCrack]

but they cleared the fighterbay a few minutes into the mission.

[karajorma]

Originally posted by Goober5000
Not in this case.  I tested the mission with the Colossus's engines all at 100%, and no matter what I tried (short of play-dead), it always turned around and headed straight for the jump node.

I'm pretty sure the mission designer just disabled it so it would stay put... that way, all the end-of-mission stuff happens reliably.  This could have been done with a source code hack also, presumably; but maybe that wasn't an option.

Why on earth is the Colossus acting differently from every other capship in the game? It does have orders to attack the Sathana oddly enough.

 I'll take a look at this later (I'm pretty busy today. I shouldn't even be here )

EDIT : Bollocks to work. Let me take a look.... The colossus moves about cause it's given orders in about 4-5 different places throughout the mission. Obviously [V] planned to have the colossus moving about but in the end changed their minds and simply disabled it without changing the rest of the mission.

Now if [V] hadn't changed that one detail things might have made a little more sense

[kasperl]

Aside from the fact that even with the first Sathanas, the colussus does not use any of it's true fighter capacity, the tactical errors made are gigantic.

If the C jumped in behind the Sathanas, it would have been easy.

If the C launched all it's fighters, it'd've been easy.

If Command used a concentrated offensive, it'd've been easy.

[Goober5000]

Originally posted by karajorma
EDIT : Bollocks to work.

Let me take a look.... The colossus moves about cause it's given orders in about 4-5 different places throughout the mission. Obviously [V] planned to have the colossus moving about but in the end changed their minds and simply disabled it without changing the rest of the mission.

That's probably it, then.  I didn't dig too deeply in the mission before... maybe I should go back and take another look.

[Flipside]

The Colossus was the GTVA 'Death Star'. And oddly enough, the Death Star made precisely the same tactical errors...

1 : A Star system is huge, why did the only place the Death Star could appear have to put the planet between it and it's target?

2 : How many fighters did that thing have, and did the Rebel time their attack to meet the pilots lunch break?

3 : Imagine how the Emperor would have felt if he'd suddenly found 80 Death Stars coming for him?

[Turambar]

Originally posted by Goober5000
Not in this case.  I tested the mission with the Colossus's engines all at 100%, and no matter what I tried (short of play-dead), it always turned around and headed straight for the jump node.

 

shows that the colossus wasnt completely devoid of intelligence, lol

no matter how dumb the ai is, it knows it can't beat a sath

[karajorma]

Yeah but the jump node in question is the Gamma Draconis one

That actually makes them dumber than they are now

[Charismatic]

Interesting, [V] planned on letting it get engins.

How was the C not complete?

Wasent it suspoe to have 12 beam cannons, 4 5 lazer turrets.. completely unbeatable by pilots, IMO, it take a very big pilot force to bring C down. I always thought if it was like sideways or in a better position, it could wipe teh Sathys ass clean, like it could hit it with 4-5 beam cannons at once.., instead of 2, and getting hammered.

I still wish they had excape pods. I never thought of the Captain- to be Heroic. It was the most stupid thing (if he had done teh same thing, even if it Had engins) to do.

Colossus running? Good.. lol. Ever gave the C waypoints to put it in best fireing position for when the Sathi comes in ?

[Grimloq]

Stoopid Command... Obviously, the Collosus can take on 80 Sathanas, but it was just a bad coincidence that it lost against just one.

Heh... At least there was a big explosion for me to enjoy.

[karajorma]

Actually this thread made me think about the mission a bit more. Look at it this way. What would have happened if the Colossus had jumped out?

The shivans had actually classified the Colossus as a threat. That's the first time they've ever done that since they went after Tombaugh station in the first game. They sent a ravana in to take out the Colossus and when that failed they actually pulled one of the Saths away from Capella deliberately to kill it.

So what would have happened if the Colossus had ran? Well it looks pretty likely that the shivans would simply have sent another Sathanas after it. You want to try sticking a Sath in "Clash of the Titans II" and seeing how easy it is then?

So maybe the Captain knew it was suicide to take on the Sathanas but did so anyway in the hope that once the Colossus was gone the Shivans would only send minor capships against the Bastion.

Taken that way he's every bit the hero that the mission debrief makes him out to be.


Of course it could be that V had other plans for the mission and screwed them up when they cancelled all the movements they had planned for the Colossus and simply disabled it. Personally I think the mission would have been much better if we never saw the Colossus die but instead saw it turning to face the Sath as the player jumped out.

[WMCoolmon]

Like I said, he could've jumped elsewhere in the system, maybe attacked the Shivan juggernaughts around the Capellan sun. The only thing I can think of that really makes sense is if there were some other forces in the system that were supposed to cover the Colossus - or maybe some sort of military force that A1 didn't know about. "We're pulling you out of there!" makes a lot more sense if Command was planning on sending other ships to cover the Colossus while it tried to escape, some secret task force, the evacuation fleet at CApella, or even the Cruisers guarding the Bastion.

[Taristin]

The colossus be damned, the ship I admire most is the GTCv Lemnos.

Lemnos here. We are going down. Repeat. We are going down. All units stand clear of the shockwave!

That right there is honor. They're all about to die, and all they can think to do is tell the remaining vessels to watch out for the blast. Selflessness to the very end.

[Charismatic]

Pilots know shockwaves of caps dont really kill any\most of them. Fs2 has sheilds remember?

I agree  w\ Kara.

[Taristin]

That's not the point. the point is the selfless act. I admire that, despite it being a game.

[Blitzerland]

Seconded. That quote really moved me. If I was the Captain of that corvette, I'd most likely be singing a different, less selfless tune.

"Ohmyeffingodweregoindown! I call the last escape pod! GET OUTTA MY WAY, UNDERLINGS! NOOOO!"

[Charismatic]

LOL@ above.
Yeah, id either go down in honor, or do down pissin my pants (so to speak). Or id be soo pissed id be cussin up a storm.

[Taristin]

I'd prefer not to know what hit me.

Which is why, if in battle, I'll stay in my quarters...