fix/emitting-events-without-backpack-loaded #35
Conversation
This file contains hidden or 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
Sadzurami
force-pushed
the
fix/emitting-events-without-backpack-loaded
branch
from
46902ce to
bdfc838
Compare
Sadzurami
force-pushed
the
fix/emitting-events-without-backpack-loaded
branch
from
bdfc838 to
30c9ac5
Compare
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.
Often we receive SO_Create messages before our backpack was loaded.
If we not handle that because of lack of backpack, we can miss important info. Same for SO_Destroy and SO_Update.
Also fixed
item.position, now that represents correct position (previously we can get 1 or -1 position if item was acquired in past and we didn't update position for this item).