csfloat / inspect

Source Code that Powers the CSFloat Inspect Link API
https://csgofloat.com
MIT License
392 stars 118 forks source link

Sticker info #197

Closed SvyatoslavArtymovych closed 7 months ago

SvyatoslavArtymovych commented 7 months ago

Hello. I remember the API was returning more information about stickers(name, wear) but now I have only stickerId and slot. Has the rest data been removed from the response? If not, how can I get it?

    "stickers": [
      {
        "stickerId": 4538,
        "slot": 3
      }
    ],

URL: steam://rungame/730/76561202255233023/+csgo_econ_action_preview%20M4652848484126482244A35394143813D4812146788585465113

SvyatoslavArtymovych commented 7 months ago

It also used to return the item name in iteminfo, but now it doesn't Full response

{ "iteminfo": { "origin": 8, "quality": 4, "rarity": 4, "a": "35394143813", "d": "4812146788585465113", "paintseed": 386, "defindex": 7, "paintindex": 1035, "stickers": [ { "stickerId": 4538, "slot": 3 } ], "floatid": "35394143813", "low_rank": 1, "high_rank": 2, "floatvalue": 0.4011116921901703, "m": "4652848484126482244", "s": "0" } }

menschma1er commented 7 months ago

haven't looked into all the underlaying packages, but sending the message to the GC myself also returned less data than before. I would also be interested in where to get a mapping stickerId<->market_hash_name

EDIT:

Well, turns out, the stickerId can be found in the items_game.txt file (tracked by SteamDatabase).

When you found the id, you can take the item_name and search for it (without the leading #) in a file called csgo_english.txt (also tracked by SteamDatabase). And there you have the market_hash_name :)))

Example: stickerId: 2107 -> item_name: #StickerKit_krakow2017_team_c9 -> "StickerKit_krakow2017_team_c9" "Cloud9 | Krakow 2017"

This seems unneccessarily laborious for just the stickername.. If there is any other way to obtain the name in one go, i would be interested in it^^ If this is the current way to go this issue can be closed.

EDIT: Havent looked into Issue 182 closely, but it seems like it fixes our issue?