Eliminated ArmorMaterial and ToolMaterial overlap #2601
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.
Closes #2600
Further information about why can be found in the linked issue.
There was discussion with @haykam821 on Discord about it not being great practice to change mappings solely to eliminate overlap and I would generally agree with that, however it seems like this is a fairly reasonable implementation choice that could become standard for developers, and the only alternative I can think of involves writing a separate class with helper methods to convert to the two interfaces depending on what's explicitly necessary and I think that's a little bit overkill for developers to implement for something so simple. That being said if it is decided that this PR shouldn't be merged for that reason, then maybe it makes sense to have a helper class like I described somewhere in fapi to aid in creating large volumes of armor and tool sets.