Hate to be a pain... but it's still not working. If I put the !endKill into the condition the trigger doesn't work at all and if I don't put it in the trigger it always works. Let me lay out how I have set up....
Okay in my Killing Trigger I have this set up
Activation is ANYBODY and set to REPEATEDLY
PRESENT and COUNTDOWN are also chosen even though I don't think countdown will do anything this way...
Type: NONE
Text: empty
Name: kill
Condition: !endKill AND this
On activation: "_X SetDammage 1" Foreach ThisList
On deactivation: empty
on the second page of the trigger I didn't change anything....
What does the COUNTDOWN TIMEOUT min: max: and mid: mean on these triggers?? I looked but didn't find much on it.
For the Countdown timer I used this one located on your site;
Count-down script
by Caelib
Snippet complexity: 2 (Simple)
Recommended for OFP version 1.46.
Views: 98
REVISION HISTORY:
1.0 - Initial Release
1.1 - Totally overhauled the script allowing it to be much more robust
1.2 - Various improvements to the script, including parameter validation
PURPOSE:
This script can be employed to create an on-screen countdown timer in a custom mission. The script is highly configurable and should meet any of your needs [should you need to keep track of time in your mission].
NOTES:
This script is open source. Feel free to copy and distribute as you like. However, please leave my credentials in-place and at least give me some credit if you use my script in a mission that you distribute. Thanks and enjoy the script! One last thing, please don't email me asking for help debugging this, or any other scripts ... that's what the forums at OFPEC are for! Enjoy.
USAGE:
To use this script, simply place the following command in a unit, vehicle, or aircraft's "Initialization" field or in an "onActivation" field. Keep in mind that all seven parameters are required.
SYNTAX:
[a, b, c, d, e, f, g] exec "countDown.sqs";
a = Number of hours. Valid values are 0 - 99
b = Number of minutes. Valid values are 0 - 59
c = Number of seconds. Valid values are 0 - 59
d = In minutes, how often to display timer. Valid values are:
-1 = NEVER show [only use this if you simply want a script timer]
0 = always show
1 = Once per minute
5 = Once every 5 minutes
10 = Once every 10 minutes
15 = Once every 15 minutes
30 = Once every 30 minutes
e = Threshold in minutes to always show. Basically, what e is for is that
when the time starts getting low, when do you want to always show timer.
Valid values are 0 - 59.
f = Label for remaining time. Use "" for no label.
g = Text to display when mission time expires. Use "" for no message.
EXAMPLE:
[1, 30, 15, 5, 10, "Time Remaining:", "Time Expired!"] exec "countDown.sqs";
This would set the mission time to 1 hour, 30 minutes, and 15 seconds. Once every 5 minutes, the user would be displayed on-screen the time remainging for the mission. When the mission time remaining reaches 10 minutes, the time would continuously count-down on-screen.
OTHER:
You will want to add a trigger [or script] with a condition "timeIsUp" that ends the mission or does whatever when the mission time has expired.
Finally, there is an additional feature that allows you to show the time remaining on-demand from within another script or on a trigger. Just remember to "deactivate" the timer in the same fashion that you triggered it ... the best way to accomplish this is via radio "go codes":
showTimeRemaining=true [activates timer and OVERRIDES ALL PARAMETERS]
showTimeRemaining=false [de-activates timer]
----------SO--------------
In the SQS file I changed timeIsUp = true to endKill = true
that SHOULD well the !endkill to become true and stop the trigger....
Is there a different way of doing the countdown timer?
Thanks for all your patience, but I brought this problem to the experts here cause I racked my brains trying to fix it. I appreciate the help I've gotten so far.