Use original vessel index as ID in bounty console #3043
Merged
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.
About the PR
In the bounty console, use the original vessel index as the dropdown item ID, not the new index.
Why / Balance
Just two lines above where the vessels are added, we sometimes skip items:
Unfortunately, later on in GetVessel, we use the item ID as an index into
_vessels
:If an item has indeed been skipped, the ID will point to the wrong index in
_vessels
! The simplest solution of all is to skip thelistIndex
dance and just use the original index, which allows us to get back to the right value in_vessels
with no hassle of any kind. Easy peasy.It appears index 1 is often something with an empty name. Unsure if this is a new bug or not, but it was recently discovered at any rate.
How to test
Media
N/A
Requirements
Breaking changes
No.
Changelog
🆑