fix: send correct tier data #2092
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
|
you sure you've tested this change ? |
|
|
The solution here is to start the iteration at 1 and not 0. |
5 tasks
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.
Behaviour
Actual
In Exaltation Forge's Transfer window: clicking tier 10 item crashes client; exalted core costs differ from tibia.fandom.com data.
Expected
In Exaltation Forge's Transfer window: clicking tier 10 item shows costs; exalted core costs are the same as on tibia.fandom.com.
Fixes #2090
Type of change
How Has This Been Tested
Tested transfers on all tiers of class 2 and 3.
Tested 10->9 and 2->1 for class 4.
Test Configuration: