BP vests?

[j-man]

I was wondering if there was any way to simulate a unit with a bulletproof vest? Mabey putting somthing in the unit int. field?

[8 Ball]

Put this in the init field of the unit

this addEventHandler ["hit", {_this select 0 setdammage 0}]

That will set the units dammage to 0 whenever it's hit.

[The-Architect]

Not in the Init line unless he's an AI unit. The player unit will be as bullet absorbant as normal. I think that the BAS Rangers have bullet proof vests. They seem to take more bullets when I shoot them anyway.

Here's the bit to make AI double hard. I'm not sure of the exact syntax.

Condition:         NotAlive joebloggs
Activation field:  Joebloggs setdammage 0

Group the trigger to joe bloggs and set it to repeatedly.
It's not very good though.  

[The-Architect]

Grr 8ball you beat me.

Showed me summit I didn't know too.
   ;D

[gundernak]

what if they got shot in the head....

Can we distinguish where the hit gone?

[8 Ball]

Yep, you can. Here's a little script I wrote. Put the script in your mission file and put this in the init field:

guy addeventhandler ["dammaged", {[_this select 0,_this select 1,_this select 2,MAXDAMMAGE] exec "BPV.sqs"}]

Note- Maxdammage is the amount of dammage the vest can take before its penetrated.
----------------------------------------------------------------------------------------------------------------------------

; Script By - 8BAll (Adam); E-mail -admd89@netscape.net
;Syntax-
;guy addeventhandler ["dammaged", {[_this select 0,_this select 1,_this select 2,MAXDAMMAGE] exec "BPV.sqs"}]
;What it all means...
;"guy addeventhandler ["dammaged", = add's the eventhandler "dammaged" to the unit "guy"
;_this select 0 = gets the name of the unit that was dammaged.(In this case the unit named "guy"
;_this select 1 = get part of body dammaged
;_this select 2 = get amount of dammage
;MAXDAMMAGE =  Put a value from 0 to 1. This is the max amount of dammage the vest can take.
 

; Define your variables
_unit = _this select 0
_body = _this select 1
_dammage = _this select 2
_maxdammage = _this select 3

;If unit is in vehicle exit
? vehicle _unit != _unit : exit

;If the bullet hit something other then the chest exit
? _body != "telo" : exit

;If dammage is greater then the max dammage exit
? _dammage >= _maxdammage : exit

;Have the unit's dammage go back to the dammage he was before as if  the "vest" stopped the bullet
_olddam = (getdammage _unit) - _dammage
_unit setdammage _olddam

exit
----------------------------------------------------------------------------------------------------------------------------

All that does is detect if the bullet hit the chest. That way the bullet can still hit the head and any where else on the body and cause guy to die.

[gundernak]

amazing... :-X

...what I actually do not understand:

;_this select 1 = get part of body dammaged

based on this what will detect which part dammaged :-\

[8 Ball]

The eventhandler will

When you add an eventhandler, you tell OFP to wait until a ceartin event happened.(And then do some sort of consequence).  When the event happens, the eventhandler returns an array with values in it. In the case of the dammage eventhandler, it returns :
                                         1-the guy who was hit
                                         2-What part of the body got hit
                                         3-How much dammage was taken by the guy.
You could use these variables in a script (use "_this select index" to pass the variables to the script) or do just about anything else you want. Thats why eventhandlers are so great. You could do a lot of stuff using eventhandlers.  ;D

Note - The different parts of the body are "nohy" for legs,"ruce" for the hands, "hlava" for the head, and "telo" for the torso

Basic Syntax for eventhandlers = unit addeventhandler ["Event" , {action}]

You can get a list of all eventhandlers in the editors depot.  

[gundernak]

thanks, clear

Is it true that eventhandlers are much faster than a trigger with condition and activation...

Because I was trying to cheating by unlimited health. In trigger's cond: getDammage and on act: setDammage...

And setDammage sometimes did not work, and my unit died, other case his health restored to max...

[desper8]

Woooo!
This $hit goes deep!!!

how comes my "help run people over question"
couldn't be answered!!!
like i said before DAMN COLLISION DETECTION
 

[Chris Death]

@8Ball,

instead of [_this select 0,_this select 1,_this select 2,maxdammage] exec "scriptname.sqs"

you could say:

[_this,maxdammage] exec "scriptname.sqs"

and inside the script you can still access the three sub-elements
of this by:

_whatever = _this select 0

_unit = _whatever select 0
_body = _whatever select 1
_dammage = _whatever select 2

_maxdammage = _this select 1


That way you could save a few nano-seconds, it takes more
to pass 2 more parameters from the EH to the script.

This might not look worth to be mentioned, but fact is:

it results in assigning one variable less than how it was
before.

May become important when there are some more shots
being fired onto that guy  

~S~ CD

[deaddog]

If you are simply trying to cheat death then do this:

#loop
~.05
player setdammage 0
goto "loop"

This should cause no appreciable lag and you can forget about the complicated code.  Unless you get hit by heavy explosives then this should do the trick.