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
https://gtm.steamproxy.vip/sharedfiles/filedetails/?id=3258972089
I obviously realise we can mouse-over each stack to find out the quantity of each stack, but this would an easier, faster way to know all of them at-a-glance. If I knew how to code, I'd do it myself, but hey-ho. Anyhow... no biggie either way, but if you happened to have the time/interest, no harm in inquiring, right? Cheers.
1.) Error in Script (30 - 64ded6) function <getObjects>: Attempting to call getObjects() on an object that does not support getObjects()
2.) Error in Script (Global): chunk_3:(537,2-38): attempt to get length of a nil value.
So it seems like it happens if you turn mod caching off. If you turn mod caching off it has to download the images of the cards and that causes the order to be messed up.