Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
Later update making a blueprint unusable is always a problem. My most important ones are pasted into a new game after update and then re-blueprinted.
Unless you are frequently swapping computers for some reason, I fail to see a good reason to use Steam Cloud and even as such there are better ways. My local files, under my control, with backups_I_made.
The best is to keep that Cloud option OFF especially to create Local Bluepritns because only the Local ones can be edited and saved on the Workshop.
That said, all the important to know have been added to the green pin of Bug Report sub forum that I strongly recommend to read all in :
Can't upload to Workshop - Workaround(s) 📌
https://gtm.steamproxy.vip/app/244850/discussions/1/3267935171647013488/
+
One shared by a SE Modder (SEModder4) in General discussions forum :
From SEModder4
For anyone having issues with not being able to Upload Blueprints/Worlds or Mods to the Steam Workshop, Here's a workaround 📌
https://gtm.steamproxy.vip/app/244850/discussions/0/3192489172307109616/