You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There should be an option to check how many hitpoints are left on gates/walls/etc.
The models of these buildings don't change when they get damaged.
Would be good to know for calculating how many satchels/bolts/etc you would need to take down a structure.
Sometimes its super confusing for people otherwise on what does damage to walls and what does not.
You see your progress when raiding other bases with explosives/melee.
I didnt test the following code, just written in a couple minutes, probably way better ways to code this...
if ((vehicle player) == player) && (speed player <= 1) && (!isNull cursorTarget) then {
_target = cursorTarget;
if ((_target isKindOf "dayz_buildings")) && (_target distance player) <= 3) then {
_checkDamage = player addAction ["Check Damage", "damagecheck.sqf", [], -1, false, false, "", ""];
} else {
player removeAction _checkDamage;
};
} else {
player removeAction _checkDamage;
};
I don't think we need such thing in DayZ. Probably not that precise. If someone decides to implement that i think it shoul show something like "Slightly damaged", "Heavily damaged" etc.
the model changing like @R4Z0R49 said is for sure the better solution
was just a suggestion untill thats implemented, so you can see if you have to hatchet for 2 or 30 minutes
There should be an option to check how many hitpoints are left on gates/walls/etc.
The models of these buildings don't change when they get damaged.
Would be good to know for calculating how many satchels/bolts/etc you would need to take down a structure.
Sometimes its super confusing for people otherwise on what does damage to walls and what does not.
You see your progress when raiding other bases with explosives/melee.
I didnt test the following code, just written in a couple minutes, probably way better ways to code this...
With
damagecheck.sqf
like this:The text was updated successfully, but these errors were encountered: