Additional check for somber weapon level #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For ER-Save-Editor/src/vm/vm.rs, line: 219
I think this is not enough to check if weapon is somber, for some save data, non somber weapon reinforceTypeId could be 2200, weapon will be consider somber and break logic in line:229, because non somber level can be greater than 10, it cause key can't be found in hash error.
I add another check, at least it will work for non-somber weapon with level > 10.
But it has problem for non-somber weapon with level <= 10.
Test:
cargo build
cargo run