Fixed ammoRange related errors
#1841
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This Pull Request fixes
ammoRangetypo (it has never been declared and I believe by analyzing the code it should beammoValue.Additionally I've added graceful fallback in a form of extra
try…catchwrapper in order to not block opening Actor Sheet, while still providing obvious Error for the users to know that something went wrong.Issue could be encountered when using worded modifiers that were not properly translated (for example item said
come armain Italian, but client was set toEnglish), or when using multipliers like*5or/5as ammo range.Should be fully compatible with #1694 Pull Request.