-
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
Add all wound types to bandage treatment configs #2886
Conversation
Gets the correct wound for the bandage treatment config Used for selecting most effective bandage and reopening _className was something like "velocityWoundMedium" but configs only had base class "velocityWound"
Messing with the configs would be a rather significant change. It's been a bit to longer for me to fully know what the effects would be of doing so without diving into the code. I rather not do that for upcoming release. I will look into this a bit more closely today. A better alternative might be to use the sqf array of injuries for the translation instead. It might already store all the necessary information. |
Array that you can easily expand with new wounds perhaps?
|
There are sqf arrays for medical that contain a lot of the config values, including the dynamically generated wound classes. They (or their C++ variants) are used for calculating new injuries. |
For configs I was thinking of something like this (bottom 3 lines are new):
|
That chance would be fine, I think. |
Fix by adding all config entries; instead of trying to modify classname
Add all wound types to bandage treatment configs
Should fix #2878
Gets the correct wound for the bandage treatment config
Used for selecting most effective bandage and reopening
_className was something like "velocityWoundMedium"
but configs only had base class "velocityWound"
Debug Output:
Another possible solution would be to add all ~21 wound classes to each bandage in
ACE_Medical_Treatments.hpp
and have the subclasses inherit?