Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Is a nice idea, I love to have more data Ever. But... Maybe is a lot of data, I think some way of select to import just some fields will be better in some cases.
About Delete... I think is not needed to delete an account, realy you are not storing more than public data of steam and what the users wants to store, like their WL and Tradables.
I think you must add something like DEACTIVATE account, their WL and Tradables will be lost and when somebody enter to the account they will see some advice like "This person has deactivated his account, contact directly tru steam on another way" or similar.
If a person wants to leave all about steam just do it in steam.
Are you considering to allow importing of all collections, or only Tradable?
Previous version displayed one game per collection because the Barter item ID was the unique key. Collections may contain the same game multiple times, therefore, the Barter item ID is no longer the unique key.
Any other data to include?
If there is no value set, should it appear at all? For example,
BTW, what is "grouping"? Tiers?
Also, to completely replace the Export feature it would be nice to have some way to obtain the games global associated data as well:
AppID, Cards, Reviews, Have, Want, Own, Bundled
In order to not overload the mydata JSON, perhaps another "gamesdata" JSON could be set up for games.
Commonly available JSON parsers can handle either case. I suggest to keep it simple and only publish what actually exists.
sku = appID for platform 1 games, subID for platform 2
grouping = tiers