allowDamage: Difference between revisions
Jump to navigation
Jump to search
Killzone Kid (talk | contribs) (see also) |
m (Bot: Replacing category Scripting Commands Arma 3 with Arma 3: Scripting Commands) |
||
Line 55: | Line 55: | ||
[[Category:Scripting Commands|ALLOWDAMAGE]] | [[Category:Scripting Commands|ALLOWDAMAGE]] | ||
[[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | [[Category:Scripting Commands ArmA2|{{uc:{{PAGENAME}}}}]] | ||
[[Category: | [[Category:Arma 3: Scripting Commands]] | ||
[[Category: | [[Category:Scripting Commands Take On Helicopters|{{uc:{{PAGENAME}}}}]] | ||
[[Category:ArmA 2: New Scripting Commands List|{{uc:{{PAGENAME}}}}]] | [[Category:ArmA 2: New Scripting Commands List|{{uc:{{PAGENAME}}}}]] |
Revision as of 16:33, 3 December 2018
Description
- Description:
- Allow or prevent an object being damaged (or injured, or killed). The command does not prevent object from taking scripted damage such as setHit, setHitIndex, setHitPointDamage or setDamage. To check if damage is allowed at current locality, see isDamageAllowed.
- Multiplayer:
- This command only works locally and must be run on all machines to have global affect.
- Groups:
- Uncategorised
Syntax
Examples
- Example 1:
player allowDamage false;
Additional Information
Notes
-
Report bugs on the Feedback Tracker and/or discuss them on the Arma Discord or on the Forums.
Only post proven facts here! Add Note
Notes
- Posted on September 2, 2013
- AgentRev
-
_object allowDamage false
has the same effect as_object addEventHandler ["HandleDamage", {0}]
(except for buildings that are native to the map; for those, the effects of HandleDamage will not sync properly across all clients, even if added to the building on every client and the server)