-
Notifications
You must be signed in to change notification settings - Fork 737
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix back blast if damage not allowed #6030
Conversation
good catch |
TRACE_1("",isDamageAllowed _x); | ||
if (!isDamageAllowed _x) exitWith {}; // Skip damage if not allowed | ||
TRACE_1("",isDamageAllowed _unit); | ||
if (!isDamageAllowed _unit) exitWith {}; // Skip damage if not allowed | ||
_unit setDamage (damage _unit + _damage); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason this is an exitWith
when it could be a then
for simplicity?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like exitWith
:)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same. But I like classical control structures even more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
classical one makes too many indents
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think I might have just been trying to minimize the git diff, which isn't really a good reason
No description provided.