[nosoop]

Originally Posted by Bacardi ...tf\scripts\items\items_game.txt Why not look from keyvalue file ?

That causes flashbacks to TF2ItemsInfo. 😱

Originally Posted by Cieniu97 If you have any suggestions how to convert valve data structure to some workable data structure (doesnt have to be in source) then I am all ears and after finishing I will happily post it on github

You can check a look at ValvePython/vdf since you're working with Python. If you really want absolutely correct names, you'll need to cross-reference the localization token (e.g. TF_Unique_MediGun_Resist for Vaccinator) with the individual translation entry stored in the game files.

I have a script that can copy specific game localization tokens into a SourceMod translation file here.

[Cieniu97]

Originally Posted by nosoop You can check a look at ValvePython/vdf since you're working with Python.

Yo! That is lit. I had to use 9 lines of code in python to get list of all items with respected names.

PHP Code:

import vdf
import json
d = vdf.parse(open('items_game.txt'))
items = {}
for l in d["items_game"]["items"]:
  print(l + " " +d["items_game"]["items"][l]["name"])
  items[l] = d["items_game"]["items"][l]["name"]
with open('allitems.json', 'w') as json_file:
  json.dump(items, json_file) 


result here in attachment, and as usual just change name from txt to json.
Nosoop you are the best!

Fallowup questions. How often does items_game change? Every update or whenever they change something inside? Is the structure of items_game consistent? Did they ever change structure of the data inside?

Thanks again!
I will still be working on how to make it generic tho

[nosoop]

Originally Posted by Cieniu97 Fallowup questions. How often does items_game change? Every update or whenever they change something inside? Is the structure of items_game consistent? Did they ever change structure of the data inside?

1. Whenever they change something related to items / attributes / qualitites / &c.
2. There are minor quirks related to keys being case-insensitive; see TF2IDB's parsing logic.
3. They historically have. You probably don't need to worry about backwards-compatible breakages these days, especially since they've moved towards protobufs for newer economy things.