Jump to content
McKay Development

Einar_100

Member
  • Content Count

    3
  • Joined

  • Last visited

  1. So from Steams point of view instead of a list of classes-values it could use some kind of identifier to the description. Anyway thanks a lot for you took the time to answer me despite it was a bit off-topic. I think I have the picture now .
  2. Thanks for your comprehensive answer and yes your assumptions were right about what i was refering to with Asset Class and Inventory provider. So an Asset Class represents a specific piece of display information of an Asset and could have been called AssetDisplayParameter instead? What confuses me most is the "conversion" of the list of classes to an asset description in the GetAssetClassInfo request. Steam can't know wich part in the response to this method belongs to which classes. So I guess Steam caches the complete signature of classes in the GetAssetClassInfo request in order to be able to re-use display information?
  3. Hi, First many thanks for the explanation of the different entitities in the Steam Asset API. It was very confusing to me before reading your post. Now, at least, I'm able to ask a question :-). This one is about the Asset Classes. Do have any thoughts about how an Inventory provider should handle these classes when mapping a number of them to a single description returned in the GetAssetClassInfo response? To me it feels like constructing an apple from a pear. How can one interpret an AssetClass? Is an Asset aggregated by a number of AssetClasses? It also seems strange that these classes are cached in Steam. What information is cached then? Only their ids? Because the Steam Asset API don't let Steam know anything about an individual Asset Class information despite the GetAssetClassInfo request (since it only returns the overall Asset information). Maybe I completely missunderstood this?! Best regards, Einar
×
×
  • Create New...