sc2: Fixed sc2 client's /received command breaking after PR 1933 merged #3497
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.
What is this fixing or adding?
After PR #1933 merged, it seems to have broken the custom
/received
command in the Starcraft 2 client. The root of the issue was that the item printout just used the default player ID of 0, but that's not considered an actual player by the decoder and it needs that information to translate a local item ID to an actual item name.How was this tested?
Ran
/received
from the starcraft 2 client with a start inventory and a few items collected from doing a mission. It now prints correctly and no longer returns a stack trace. Didn't test this with items that were collected by slots playing a different game, not sure if that's a potential issue.If this makes graphical changes, please attach screenshots.
None