- Modified GetValueOfAttribute to use the actual definition from the stored attribute
- Added test to verify maximum value is respected from stored definition
- All 37 tests pass
Co-authored-by: sven-n <5238610+sven-n@users.noreply.github.com>
Made it possible to use another attribute as operand, instead of a constant float value. This will make some calculations easier, e.g. we can use it for conditional bonuses. Example: Give a bonus only if an item with a specific attribute is equipped. This comes up in a lot of master skills, e.g. a damage bonus only when wearing a two-handed sword.
The most changes are obviously by usage of the global using and file namespace features.
Additionally, because I was in a flow, I changed all private field names to start with an underscore.
