RepairRate woe

#1 Try it like this:

%obj.schedule(3000, "resumeRepair");

#2 Isn't.. that what it is?

#3 Note the " "

#4 You need to pass the %obj


%obj.schedule(3000, resumeRepair, %obj); instead of what you have

I think :)

#5 @Tim: There's really no difference though, that was one of the variations I tried, same effect.

@Mr Meikel: Nope, nothing. No console reports on anything either.

Edit: Ah, got it.

function Player::resumeRepair(%this)
{
   %this.setRepairRate(0.4);
}



function Armor::damage(%this, %obj, ...)
{
   ...

   %obj.setRepairRate(0); // This stops the repair
   %obj.schedule(5000, resumeRepair); // lets the repair continue after 5 seconds

   ...

Only trouble is, I want the last damage taken to set the countdown to 5 seconds before it repairs. Say I get damaged, then in 5 seconds the repairRate will be set to 0.4. Well if I got damaged two seconds after the initial damage, I'll heal in 3 seconds, since the schedule was called already from the initial damage to, in five seconds, set the repairRate back to 0.4.

#6 Well I got it working perfectly by doing this in Armor::damage:

%obj.setRepairRate(0); // This stops the repair, works.

   if ($repairSchedule) { cancel($repairSchedule); }

   $repairSchedule = %obj.schedule(5000, resumeRepair);

I'm just curious if those nice little dollar signs will function right if you're in a networked game.

#7 Why store it as a global variable?

%obj.setRepairRate(0);
if (%obj.pendingRepairScheduledEvent) 
{
  cancel(%obj.pendingRepairScheduledEvent); 
}
%obj.pendingRepairScheduledEvent = %obj.schedule(5000, resumeRepair);

#8 Yeah, storing it as a global will cause you grief if more than one player is going to repair.

#9 Thanks Stephen. :)