Problem with score system

#1 Unfortunately the problem is that the sourceObject and sourceSlot properties get deleted 7 ticks after the projectile is sent on it's way. This has often been mentioned as a feature intending to disable/enable projectile collision to prevent a weapon firing and having the projectile collide with the owner.

A way to work around this is to substitute a new dynamic property when you spawn a projectile, and reference this new property in the damage and projectile callbacks instead of the self-deleting ones.

Granted this should have been fixed long before now, but it is such a simple thing...

#2 Oh I see, It should become a little resource for people to reference, you know.

#3 Since I'm getting a bit better at this scripting thing any chance you could cook up some example code?

#4 In projectile.cc, search for this bit of code near the top of ::processTick

if(mSourceObject && mCurrTick > SourceIdTimeoutTicks)
   {
      mSourceObject = 0;
      mSourceObjectId = 0;
   }

Just comment that out, and the sourceObject information shouldn't be deleted.

#5 That shouldn't create the problem that it was implemented for? Like having the projectile explode in my face?

#6 Nope. When the projectile is created, it ignores the sourceObject anyway (to my understanding). That block of code that I posted deletes the source object info after it hits something, I'm not sure why. I've had that disabled for a long time without any issues.

#7 Alright sounds like a plan, thanks a bunch.

#8 There's also another issue that needs a'fixin. Have a look at your projectile ::onCollision methods:

function CrossbowProjectile::onCollision(%this,%obj,%col,%fade,%pos,%normal)
{
   // Apply damage to the object all shape base objects
   if (%col.getType() & $TypeMasks::ShapeBaseObjectType)
      %col.damage(%obj,%pos,%this.directDamage,"CrossbowBolt");

   // Radius damage is a support scripts defined in radiusDamage.cs
   // Push the contact point away from the contact surface slightly
   // along the contact normal to derive the explosion center. -dbs
   radiusDamage(%obj, %pos, %this.damageRadius, %this.radiusDamage, "Radius", %this.areaImpulse);
}

You'll see that the first argument of the damage and radiusDamage calls, which specifies the shooter (sourceObject), is %obj. The issue with that is %obj in that context refers to the projectile object, not the shooter.

For everything to be hooked up properly, you'll need to change those arguments to %obj.sourceObject:

function CrossbowProjectile::onCollision(%this,%obj,%col,%fade,%pos,%normal)
{
   // Apply damage to the object all shape base objects
   if (%col.getType() & $TypeMasks::ShapeBaseObjectType)
      %col.damage(%obj.sourceObject,%pos,%this.directDamage,"CrossbowBolt");

   // Radius damage is a support scripts defined in radiusDamage.cs
   // Push the contact point away from the contact surface slightly
   // along the contact normal to derive the explosion center. -dbs
   radiusDamage(%obj.sourceObject, %pos, %this.damageRadius, %this.radiusDamage, "Radius", %this.areaImpulse);
}

That'll do it. Now, when a player is killed by projectile damage, the sourceObject is properly handed off to Armor::damage() in player.cs. The client object is determined, GameConnection::onDeath() is called, and the scoring happens as it should.

#9 Alternatively, just do this:

//
   if(mSourceObject && mCurrTick > SourceIdTimeoutTicks)  
   {  
      mSourceObject = 0;  
      //mSourceObjectId = 0;  
   }

This removes the pointer mSourceObject, but retains the ID number mSourceObjectId, which is the one that scripts can access. If I remember correctly.

Removing all that stuff entirely will mean that mSourceObject will never be struck by that projectile. Depending on your game, this may be fine.