安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题
People just think they're cool commenting something a thousand times when it's not even on topic/right, they don't bother to read, to verify something, or just think they only want "attention" and it's not even that
Verse.LongEventHandler:RunEventFromAnotherThread (System.Action)
Verse.LongEventHandler/<>c:<UpdateCurrentAsynchronousEvent>b__28_0 ()
System.Threading.ThreadHelper:ThreadStart_Context (object)
System.Threading.ExecutionContext:RunInternal (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool)
System.Threading.ExecutionContext:Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool)
System.Threading.ExecutionContext:Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object)
System.Threading.ThreadHelper:ThreadStart ()
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Verse.Log:Error (string)
Verse.Steam.WorkshopItem:MakeFrom (Steamworks.PublishedFileId_t)
Verse.Steam.WorkshopItems:RebuildItemsList ()
Verse.Steam.WorkshopItems:.cctor ()
Verse.ModLister:RebuildModList ()
Verse.ModLister:.cctor ()
Verse.ModsConfig:.cctor ()
Verse.LoadedModManager:InitializeMods ()
Verse.LoadedModManager:LoadAllActiveMods (bool)
Verse.PlayDataLoader:DoPlayLoad ()
Verse.PlayDataLoader:LoadAllPlayData (bool)
Upon inspection found that the HugsLib WAS in fact created but with the workshop number 3513818909. This is strange. It might even break my save.
please fix it !
[net.pardeike.rimworld.lib.harmony] Patches on methods annotated as Obsolete were detected by HugsLib: Verse.Translator.Translate
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Verse.Log:Warning (string)
HugsLib.Utils.HarmonyUtility:LogObsoleteMethodPatchErrors ()
HugsLib.Utils.HarmonyUtility:LogHarmonyPatchIssueErrors ()
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.LongEventHandler.ExecuteToExecuteWhenFinished_Patch0 ()
Verse.LongEventHandler:UpdateCurrentAsynchronousEvent ()
Verse.LongEventHandler:LongEventsUpdate (bool&)
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.Root.Update_Patch1 (Verse.Root)
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.Root_Entry.Update_Patch0 (Verse.Root_Entry)
I'm reading it almost everywhere.
DawnGlow, you're the sht 🎉
My take is that, eventually, there is not that much value in using HugsLib in the age of RimWorld 1.6; most HugsLib features are already available in some form in the vanilla game, or in other community tools.
But, some HugsLib features are still not vanilla available (eg showing update news, convenient shareable error logs, etc), so HugsLib is still valuable.
It's more like risk aversion thinking and the so-called "vendor lock-in": if there aren't too much features that must require HugsLib, and when HugsLib is shown to be slow on updates (o7 to HugsLib tho), then might as well migrate away from HugsLib.
Until HugsLib Original is updated, continue to use this to get by. Unknown if the mods that updated at similar time to the HugsLib Original update will have bugs or be affected by using the Abridged(id=3513789221 YOU ARE CURRENTLY HERE) for now.