Hmm it should work in any order and definitely print the else message as well.
It did actually run the "else" condition, I just couldn't get it to work both ways and assumed it was because I was too slow.
The reason I believe it cannot work both ways is because of the way the logic statement is setup, with:
Code: Select all
level.death_time[local.name2] - level.death_time[local.name1]
Assuming my killspan = 3 seconds, the condition = 3 for [local2 minus local 1]. However, the number is -3 if I kill in the other order. I think that a negative number is a bad number or something, unless you have a means of dealing for the negative condition built into the code.
Otherwise, the code works wonderfully.
Are you trying to make a killing spree mod?
I like the way you guys think. Answer = . . . somewhat, yes. There are some spots in my map that have a nice amount of generic human AI. I feel that a quick trigger finger deserves an audible reward. So far, I have 3 possible Doublekills, (Thank you JV) and one Triplekill, which is made of a combo with two other existing baddies.
I am assembling a cooperative play objective map, which requires players to storm a huge concrete bunker, and do . . . stuff . . . which I cannot spoil at this time.