[Snail]

The Venom cruise missile has a turret

One second... what if we use a normal model(with shields) as bomb? Is it going to keep the shields? There are a few screenshots of Erynies torpedoes and other interesting stuff somewhere.

Wasn't that takashi?

[Mobius]

Did the torpedo keep the shields?

[Colonol Dekker]

Kamikaze flag ftw!

[Snail]

Did the torpedo keep the shields?

No. It might even have made it easier to hit.


On the topic of adding features, how hard could it really be to add another legal flag to the Subsystem flags field which automatically destroys the ship when the subsystem is destroyed (without having to have SEXPs)?

[Mobius]

SEXPs work fine. And what if you don't want a ship to blow up after the destruction of a certain subsystem?

[karajorma]

On the topic of adding features, how hard could it really be to add another legal flag to the Subsystem flags field which automatically destroys the ship when the subsystem is destroyed (without having to have SEXPs)?

Harder than telling the FREDder to not be so ****ing lazy and just use a SEXP.

[WMCoolmon]

Actually, that seems kind of useful if you wanted to consistently make a 'cockpit' subsystem for fighters that would blow the thing up (kill the pilot, fry the electronics, reactor goes critical). Could add some variety to things.

[FUBAR-BDHR]

The feature that I always though would be nice is a way to tell if a player shot down a bomb and be able to assign a point score to the bombs.  Also tracking bomb kills in player stats would be nice.  Kind of a way to reward a player for playing good defense. 

[Mobius]

It would be useful in a StarLancer MOD.

[Koth]

Slightly related question: Is there a limit on how many flags a ship or a weapon can have?

[blowfish]

Slightly related question: Is there a limit on how many flags a ship or a weapon can have?

From what I saw in the code, there is none, though eventually you will run out of memory (that's not likely to happen any time soon though).

[karajorma]

Slightly related question: Is there a limit on how many flags a ship or a weapon can have?

Practically, once we hit 32 flags we have to add a new section (Which is why each ship in the mission file have a Flags() and a Flags2() section). Apart from that I can't think of one.

[Polpolion]

What about dampening for missiles? Is that even remotely possible?

[blowfish]

What about dampening for missiles? Is that even remotely possible?

Actually there is a roation dampening number that is automatically set to 0 but could become a weapons.tbl option the same way custom hitpoints could.  Not sure about speed though.

EDIT: Speed can be dampened too.

Does anyone know the significance of this like of code from weapon.cpp:

Code: [Select]

objp->shield_quadrant[0] = wip->damage;

[blowfish]

EDIT: Double post.  Whoops!

[Polpolion]

With my 4 weeks of c++ classes, I am going to conjecture that the line applies the weapons damage to whatever shield quadrant objp might be pointing to, assuming it is a pointer at all, and completely disregarding whatever "wip" is.


Damn. The hardest part of trying to learn how to code the SCP is figuring out what the hell all those variables/pointers/abbreviated prefixes/classes/whatever are. BTW, any tips on learning that, aside from just sitting down and reading the entire code?

EDIT: Nevermind, I should probably just learn how to program first.

[Turey]

objp stands for object pointer, wip stands for weapon info pointer (pointer to weapon_info struct)

[karajorma]

Does anyone know the significance of this like of code from weapon.cpp:

Code: [Select]

objp->shield_quadrant[0] = wip->damage;

My guess would be that it's some kind of error which has been hidden by the fact that weapons can't have shields. The current version was added by Phreak but is merely a change from this

Code: [Select]

objp->shields[0] = wip->damage;
I can't think why a weapon's damage would be stored in the shield array. You should get that info out of Weapons_info when you need it.

[Mongoose]

Damn. The hardest part of trying to learn how to code the SCP is figuring out what the hell all those variables/pointers/abbreviated prefixes/classes/whatever are. BTW, any tips on learning that, aside from just sitting down and reading the entire code?

That's kind of the conundrum I was faced with when I started playing around with downloading/compiling the source.  I've taken a few C/++-related classes, so I feel like I probably have enough technical knowledge to make at least a tiny contribution to the project...but after looking at that mass of files and directories, I realized that, even were I to pick what seemed like a relatively minor bug in Mantis and try to start working on it, I'd have no idea at all where to go.  I suspect that the only way to get anywhere is to just grit your teeth and start hopping between files.

[karajorma]

You can pick up a good amount of how the game works from just looking at the structs in object.h, ship.h and weapon.h

Many of the variables ending in p are a pointer to to an object in one of the arrays from those files. sip = Ship_info pointer, wip = Weapon_info pointer etc. Your IDE probably has a way to leap to the definition of any variable easily, use it.