---
name: "allowDammage"
type: command
status: ok
groups: ["Object Manipulation"]
arma3_since: "0.50"
locality: {"argument": "local", "effect": "global", "server_exec": false}
source: https://community.bistudio.com/wiki/allowDammage
revid: 310281
updated: 2022-05-05T13:11:25Z
---

# allowDammage

*Command · Object Manipulation · Arma 3 v0.50 · introduced in Operation Flashpoint v1.00*

Locality: arguments **local** · effect **global**

Alias: [allowDamage](../commands/allowDamage.md)

## Description

Allow or prevent an object being damaged (or injured, or killed). The command does not prevent object from taking scripted damage such as [setDamage](../commands/setDamage.md) or [setHit](../commands/setHit.md).

## Syntax

```sqf
object allowDammage allow
```

**Parameters:**

- `object`: [Object](../topics/Object.md)
- `allow`: [Boolean](../topics/Boolean.md)

**Returns:** [Nothing](../topics/Nothing.md)

## Examples

### Example 1

```sqf
player allowDammage false;
```

## Multiplayer

> [!IMPORTANT]
> The command has to be executed where the object is [local](../topics/Multiplayer_Scripting.md#locality) and will be effective as long as the object does not change locality.
> If the object changes locality, the command needs to be executed again on the new [owner](../commands/owner.md)'s machine to maintain the effect.

## Problems

This command did nothing until Arma 2.

## See also

[setDamage](../commands/setDamage.md) · [damage](../commands/damage.md) · [allowDamage](../commands/allowDamage.md)

<sub>Source: [BI Community Wiki — allowDammage](https://community.bistudio.com/wiki/allowDammage) (revision 310281).</sub>