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)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese)
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
I did in fact look at trying to do this in a better way using the Scribe logic but it seems that the Rimworld Scribe API is made up of static classes and singletons which makes it difficult if not impossible to re-use without some kind of crazy reflection based mokey patching or similar. Its a pitty as it would have been nice to be able to use this same API.
One alternative possibiltiy I did consider was to create a facade/interface that you could write to that could be reified as either the Scribe API or another implementation that would write to a seprate directory (i.e. saving CE loadouts). The benefit here is that you wouldn't need to duplicate logic between saving the save game file and saving other to other types of files but this seemed massively over-engineered for my small change.
One thing to be aware of is if you kept how I write/read the files in Save Storage Settings is not xml/standard rimworld. Depending on where CE is with keeping to standards you may need to change that code to use Scribe.
In either case I don't mind and thank you for letting me know!
the latest updates seem to break everything and causes anything in the storage to not show up