-
Notifications
You must be signed in to change notification settings - Fork 736
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
Medical - Add more conditions on when the PAK can be used (#7682) #7684
Conversation
Co-authored-by: Filip Maciejewski <veteran29@users.noreply.github.com>
- Removed unnecessary whitespace on LN 46 - Call global var directly at LN 87 - Updated Wound Reopen Chance localized name & description
- Increased reopen coefficient upper limit from 2 to 5.
Is this still WIP or ready? |
Haven't gotten around to testing it in a multiplayer environment yet unfortunately. |
Please add a setting to not allow PAKs when the patient has untreated fractures. |
|
||
|
||
// Require stitched wounds. | ||
if (EGVAR(medical_treatment,requiredWoundStatePAK) == 2 && { !(count GET_OPEN_WOUNDS(_unit) == count GET_STITCHED_WOUNDS(_unit)) }) exitWith {false}; |
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.
For similar reasons as the "require at least bandaged wounds" check, I think this can also fail. I think you just want to check that there are no bandaged wounds with amount > 0. reference
if (GET_BLOOD_VOLUME(_unit) < _requiredBloodVolume) exitWith {false}; | ||
|
||
if (EGVAR(medical_treatment,allowPainPAK) == 0 && { IS_IN_PAIN(_unit) }) exitWith {false}; | ||
if (EGVAR(medical_treatment,allowFracturesPAK) == 0 && { !(GET_FRACTURES(_unit) isEqualTo []) }) exitWith {false}; |
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.
Use isNotEqualTo
.
if (EGVAR(medical_treatment,allowFracturesPAK) == 0 && { !(GET_FRACTURES(_unit) isEqualTo []) }) exitWith {false}; | ||
|
||
// Require at least bandaged wounds. | ||
if (EGVAR(medical_treatment,requiredWoundStatePAK) == 1) then { |
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 you also want to check this when stitched wounds are required.
Thanks for the review. I will get to this when able. |
I don't expect to be able to make time for this any time soon due to work. All help is appreciated in making the minor changes required for this PR to be approved & merged. Thanks. |
Latest review changes addressed in anden3#5 and awaiting merge. |
One question: I've updated the default However, I've long felt that PAKs bypassing stitching effectively makes stitching redundant, and player behaviour in my community has reinforced that. @mharis001 -- Do you feel that stitched wounds should be required for PAK application by default? |
…ted successfully.
I think the default should reflect the behaviour prior to these settings being added. |
My 2c: Let the community choose if they wanna go such ultra-realistic by introducing a setting, just like the options which only allow stitching in a medical vehicle, cuz I think having to stitch+PAK is ridiculously tedious in the long run. And create rules in the community and make the settings accordingly ! For ex in our group, it varies between medics how they use both: some will postpone both until it's quiet (which is a mistake a lotta the time) but 99% the time will just PAK when it's quiet, I use PAK every time the action or man shortage ain't too bad compared to how long PAKking takes, and I use stitching only if either PAK takes way too long due to bruises or something, or the patient is unconscious and in a dangerously bad condition. Hell, a lotta the time we don't have stitching available. ^ Besides, you could require the use of medical facilities for stitching like we use the FSG Medic Bag from Workshop, which forces the medic (and mission maker) to think further. |
Hopefully finishing this PR once and for all...
@mharis001 Changes merged in from fork. Please review when able. Build failure appears related to the changes in the build process since this PR was opened? My changes should not be causing them. |
@PabstMirror Any update on this? I've addressed all requested changes, but, due to the build pipeline changes, I cannot proceed without guidance from the curation team. This is further complicated by not being the author of the PR. Any and all help in finally getting this PR merged is greatly appreciated. Thank you. |
Apologies for bothering again, but, see above. I cannot proceed without assistance. @mharis001 as well. |
Co-Authored-By: André Vennberg <andre.vennberg@gmail.com>
I have rebuilt this PR's work into a clean and working state in #8964. |
Closed due to being succeeded by #8964. |
When merged this pull request will: