Some fixes to Steam_UGC functions#249
Merged
Merged
Conversation
CreateQueryUserUGCRequest()Steam_UGC functions
5 tasks
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
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.
Some apps may request UGCs by calling
CreateQueryUserUGCRequest()with appids corresponding to the item creation tool and the app itself respectively, which may be different. Contradictory to the doc, real steam actually does return a valid handle and correct results by further callingSendQueryUGCRequest(). However it seems that the appids indeed somehow affect the returned UGCs, and thus more info is needed to emu it. Currently I choose to just remove the too strict check only.Some apps require metadata for UGCs to work, so a new option is added to support such behavior.