Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
As long as you aren't getting any noticeable issues you can probably ignore them. I find it unlikely that it's coming from the scenario though as I've used old scenarios myself and that kind of information shouldn't be saved in it anyway.
In v1.5 the worktype FSFRefueling no longer exists and the worktype FSFLoading was renamed to FSFTransport. The log isn't showing where these errors are coming from exactly. I can only assume its either coming from another mod referencing the old worktypes or its something to do with your savegame, which could maybe occur if you took a save from v1.4 and continued it in v1.5.
I'm getting this error popping out for quite sometime. Ive tried validating RimWOrld install files many many times, unsub and resub the mod multiple times and even did a full uninstall and clean install alas, the error remains.
Could not resolve cross-reference to Verse.WorkTypeDef named FSFRefueling (wanter=workTypes)
Could not resolve cross-reference to Verse.WorkTypeDef named FSFLoading (wanter=workTypes)
U
Could not load reference to Verse.WorkTypeDef named Rescuing
Null key while loading dictionary of Verse.WorkTypeDef and System.Int32. label=settings
Logs are at:
https://gist.github.com/HugsLibRecordKeeper/2b812c31384241a68205ef0fe764ab87
I also replied to your comment in the bug report thread. Don't worry, nobody ever reads the mod description, it comes up way too often.
https://cdn.discordapp.com/attachments/1048784503017046107/1242785560452530208/image.png
Steam has been pretty wonky about doing mod updates for quite a long time leading to a lot of people using outdated mod versions. As you've found sometimes even trying to force it to update them doesn't work for some reason. Looking at the change log that specific error was fixed over a month ago. I personally go through the updates section and unsubscribe and resubscribe to mods individually to hopefully ensure they update properly. So far I haven't had any issues but maybe I'm just lucky in that regard.
Steam must be acting stupid and downloading the wrong version because that error is definitely fixed. I checked the files to be sure. If manually unsubscribing and resubscribing isn't working you could try asking steam to verify the game files. If none of that works you can go to the change log tab and hit the download button on the newest update. That will give you a copy of the latest version which you can use to replace the files.