-
Notifications
You must be signed in to change notification settings - Fork 276
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
feat: Armor values specified directly in armor JSON #3930
Conversation
maybe it'd be better if overrides could be defined using #2776 |
Will do, it may be a source of conflict otherwise. EDIT: ...Or not. It won't conflict, so I'll keep this one small for now. |
alright. in my opinion, while manually overriding armor values could be useful in some cases, i'd like the material system to get more love, e.g computing various armor stats from material composition |
That could be cool if we could manage it, but so far, the material system has been more of a hindrance than a benefit. |
Still compiles but pretty error spammy, both seem to be caused by this PR? |
Purpose of change
Allow fine-tuning armor values, without having to rely on materials and material thickness.
Describe the solution
Armor item type now has an extra field: "resistance".
It looks like this:
If this field is specified, armor values from materials and thickness are ignored.
Note: if armor override is specified, armor values are not reduced when the armor is damaged.
Describe alternatives you've considered
Testing
Additional context
Checklist