fix: commendation vendor cant accept missions #1497
Merged
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.
We never set the HasStandardCost flag in the AchievementVendor.
"Why are you calling RefreshVendor again in the most derived class constructor? Wont the one in VendorComponent call it?"
No because at that point in time, the vftable for the AchievementVendor has not been assigned yet and as such a call to the virtual function is impossible. We do need the function to be virtual to prevent the regular refresh from going through as the work is unnecessary for this entity
Tested that you can complete missions from the AchievementVendor and still buy still.