-
Notifications
You must be signed in to change notification settings - Fork 740
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 Pain Unconscious Threshold setting #8394
Conversation
Add PAIN_UNCONSCIOUS slider to ACE Medical settings
I believe this was an intentionally hidden setting? |
Why? What is the point? |
See #7236 for the introduction of these constants. I would tend to agree with the original reasoning, but I'm admittedly pretty picky about our settings UX. If we were to introduce settings for things like this I'd like to see us improve the presentation with a clear separate "ACE Medical (Advanced Settings)" category for things which we want to say don't need to be changed, but can be for power editors who want to really fine tune behaviour. Also I don't like that you changed the conditional logic with no justification 😛 |
And? They are already moved from constants to variables with reason
No reasoning on that. May be just laziness.
Then all that magic must be described in wiki
You can close this PR. But, please, mention var in wiki. |
I was providing context to this (intended to be) collaborative change proposal discussion.
It seems reasonable to infer that the reasoning is because they are not behavioural modifiers that warrant settings as they're not relevant to 99% of users (i.e. are overkill).
I agree that documentation is good. However, sometimes in software you want to expose things for power users without forming a "contractual agreement" (i.e. formally declaring a public API) to maintain them in future versions (knowing that power users are accepting the responsibility to keep their downstream code up to date). That's not necessarily the case here, but one possible explanation.
Thank you for providing justification, I agree that there's an inconsistency there (although the outer condition being more restrictive makes more sense if you think about the intersection of those).
Personally I think context dependent. You would call 50% the threshold for a majority right? Now would you call precisely 50% a majority? |
Co-authored-by: Salluci <69561145+Salluci@users.noreply.github.com>
Co-authored-by: jonpas <jonpas33@gmail.com>
UX would benefit from switching the hardcoded values to the variable here: ACE3/addons/medical_gui/functions/fnc_updateInjuryList.sqf Lines 74 to 86 in efe0968
|
Pain always in 0-1 range. I don't see who and when need to change this localization switch. |
Since the february pain system redesign update had consequences on This request should be reconsider to adapt players preferences. Effect of what was at 0.5 default value is more like 0.35 or ~0.4 now. Which I recommand as default value. |
I think this is valid to have as a setting. We can move it to a separate settings menu if it ends up being an issue, I've been meaning to categorize the medical settings independently anyway. |
@@ -34,6 +34,15 @@ | |||
true | |||
] call CBA_fnc_addSetting; | |||
|
|||
[ | |||
QEGVAR(medical,painUnconsciousThreshold), |
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.
QEGVAR(medical,painUnconsciousThreshold), | |
QUOTE(PAIN_UNCONSCIOUS), |
technically it could be this I don't really like it and would rather keep it as is
When merged this pull request will: