Indirect kills by missiles, like kills by fires created by the inbuilt inferno missiles, won't credit whoever launched the missile if their the killing hit. This also applies to slave launched missiles.

This is a known issue ~ however, this isn't entirely correct.

If you use a MIRV, and the baby missiles get a kill and the parent is still alive you'll get XP. If the parent has self-destructed, you won't.


There's nothing that can be done about this: I've already extended the lifespan of the MIRVs once. Consider it an indirect "optimal strategy" when choosing your distance to launch.

What if launching a MIRV creates an invisible, untargetable, invulnerable, untractorable controller object that spawns in a random direction away from the player ship and causes the children missiles to be spawned on the original missile? Then have it so that once all of the missiles are destroyed, the controller destroys itself.

Essentially, it's just making the launched MIRV look like a parent when it really isn't.

I have no clue how the code works, but it's just a suggestion.

I honestly have no idea what a MIRV is, im just tired of my inferno slaves stealing kills with their missiles.

If it's possible to code a controller object it should fix the problem, but I'm not a coder.

That's just asking for trouble and probably needs more coding than just fixing the actual problem