[Bobboau]

this was V's doing by the way,
look at maybe_hack_cruiser_chase_abort()
for those of you unable to look at the source at the moment it goes a little something like this

Code: [Select]


int maybe_hack_cruiser_chase_abort()
{
ship *shipp = &Ships[Pl_objp->instance];
ship *eshipp = &Ships[En_objp->instance];
ai_info *aip = &Ai_info[shipp->ai_index];

// mission sm3-08, sathanos chasing collosus
if ( stricmp(Mission_filename, "sm3-08.fs2") == 0 ) {
if (( stricmp(eshipp->ship_name, "colossus") == 0 ) || ( stricmp(shipp->ship_name, "colossus") == 0 )) {
// Changed so all big ships attacking the Colossus will not do the chase code.
// Did this so Beast wouldn't swerve away from Colossus. -- MK, 9/14/99
//if ( stricmp(shipp->ship_name, "Sathanas") == 0 ) {
// do cool hack stuff here
ai_clear_ship_goals( aip );
aip->mode = AIM_NONE;
return 1;
//}
}
}

return 0;
}


basicly it says that if the mission file name is sm3-08.fs2 (my eyes bleed already) and ether our ship or the ship we are atacking's name is colossus, don't do anything.

sm3-08.fs2 == 'their finest hour'

[Setekh]

!

They must have been running out of ideas. Or coffee, at 3am.

[IceFire]

Wouldn't it just make sense to set the Sathanas on a waypoint and let the Colossus orbit it with its guns?  I thought thats how it had been done...

[Taristin]

...mission specific coding?

[phreak]

i found an uglier one!!11

Code: [Select]


// For the subspace mission (sm3-09a)
// for delta wing
// if they're sufficiently far into the mission
// if they're near one or more enemies
// every so often
// fire a synaptic if they have one.
void maybe_cheat_fire_synaptic(object *objp, ai_info *aip)
{
// Only do in subspace missions.
if ( The_mission.flags & MISSION_FLAG_SUBSPACE ) {
ship *shipp;
int num, time;

shipp = &Ships[objp->instance];

if (!(strnicmp(shipp->ship_name, NOX("delta"), 5))) {
num = shipp->ship_name[6] - '1';

if ((num >= 0) && (num <= 3)) {
time = Missiontime >> 16; // Convert to seconds.

time -= 2*60; // Subtract off two minutes.

if (time > 0) {
int modulus = 17 + num*3;

if ((time % modulus) < 2) {
int count = num_nearby_fighters(get_enemy_team_mask(OBJ_INDEX(objp)), &objp->pos, 1500.0f);

if (count > 0) {
cheat_fire_synaptic(objp, shipp, aip);
}
}
}
}
}
}

}



[Bobboau]

shouldn't they be doing that in every mission?
that behavior, not that code

[deep_eyes]

im guessing its a programed scripted sequence of events?

[CP5670]

I think that Colossus thing would have been much easier to do by just not giving them attack orders and using some fire-beams instead...

Look for any such thing in the source regarding sm3-10 and end-campaign; there is a bug in the last mission that might have had such a hack to correct it but was removed at some point, since the bug has suddenly started to show up.

[Knight Templar]

So what you're saying is that the Colossus really sucks more than we know? *gasp*!

[Nico]

Originally posted by PhReAk
i found an uglier one!!11

Code: [Select]


// For the subspace mission (sm3-09a)
// for delta wing
// if they're sufficiently far into the mission
// if they're near one or more enemies
// every so often
// fire a synaptic if they have one.
void maybe_cheat_fire_synaptic(object *objp, ai_info *aip)
{
// Only do in subspace missions.
if ( The_mission.flags & MISSION_FLAG_SUBSPACE ) {
ship *shipp;
int num, time;

shipp = &Ships[objp->instance];

if (!(strnicmp(shipp->ship_name, NOX("delta"), 5))) {
num = shipp->ship_name[6] - '1';

if ((num >= 0) && (num <= 3)) {
time = Missiontime >> 16; // Convert to seconds.

time -= 2*60; // Subtract off two minutes.

if (time > 0) {
int modulus = 17 + num*3;

if ((time % modulus) < 2) {
int count = num_nearby_fighters(get_enemy_team_mask(OBJ_INDEX(objp)), &objp->pos, 1500.0f);

if (count > 0) {
cheat_fire_synaptic(objp, shipp, aip);
}
}
}
}
}
}

}

[/B]

Whoa, trop chouette, là on comprend vraiment tout, j'adore. Merci, non, franchement, j'insiste, merci.

[kasperl]

dude, ****.

mission specific coding is something i never expected in any usefull bit of code. they must've run out of FREDders, and have too much coders or something.

what happens when you make a compeltely different mission with the same filename?

[RandomTiger]

Not much we can do about it, we have to maintain compatibility with the default data.

[Nico]

The mission could be fixed so you can get rid of that crap?

[RandomTiger]

We need the code to work the default data.
Its all very well saying oh we will give them the fix,
but some people may never download the vp.
And in my opinion the vp should not be compulserary.

[RandomTiger]

Nico, I dont see why that one is so bad, its generalised to subspace missions. However I have to agree the one Bob found is quite a bad hack.

[Nico]

I don't see why THAT ONE is so bad either, I don't even understand what it is ( since phreak believes everybody can read code ), but ten, twenty of those, and that's how you get a bloated code filled of lines useful for one single occurence in the game. Well dunno, I had the feeling that "cleaning the code" included stuff like that...

[aldo_14]

Originally posted by Nico
I don't see why THAT ONE is so bad either, I don't even understand what it is ( since phreak believes everybody can read code ), but ten, twenty of those, and that's how you get a bloated code filled of lines useful for one single occurence in the game. Well dunno, I had the feeling that "cleaning the code" included stuff like that...

Says in the comments...basically tells Delta wing to fire of a synaptic every  few minutes if posssible.

How often are these functions called/checked?  upon every mission?

[Bobboau]

every frame

[diamondgeezer]

They even managed to misspell 'Sathanas'. The code seems to apply to the Ravana 'Beast' as well. My personal favourite bit is where it says 'do cool hack stuff here'

[Flaser]

IMHO Get rid of it and all of its brothers/sisters.

The SCP is no longer in a phase where you will have any justifiable benefit from using the new exe without any supplementary data.