安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
10 
举报此帖
@nubcake you can go to github and get one of the previous releases.
I'm using 7.0.0 and for my mods it works, 7.0.1 is when stuff breaks
Just a possible workaround until they get this stuff sorted proper
Edit: release 7.0.0 seems fine so far
I tried the following -
Copied 6.2.1 to the hugslib folder
steamapps/workshop/content/294100/818773962
However when I relaunch the game it auto updates to the new version.
I tried disconnecting from the internet and relaunching but my entire modlist had then vanished from the game.
In the game's mod manager select the HugsLib with version 7.0.0 and unselect the 7.0.1 one.
(They will have different icons and different versions)
Disclaimer: if you have other mods updating to the newer Harmony version the problem will probably persist and you'll have to rollback/disable those mods too
No worries, I also had to dabble some folders back and forth to figure it out.
Btw, if you want to "save" that working installation so it isn't broken by updates, you can make a copy of the game's folder and then copy all the workshop mods to the Mods folder.
This way you'll get a backup installation that will work with mods (even offline) and won't be broken by updates.
@TemplarX: I actually did this before your suggestion, thanks again for helping. :o)
I do recommend that, yes- 7.0.1 is the update that includes the Harmony 2.0.0.7 version, which we will be using going forward. Still, your mod may work as-is, depending on the extent of patching you do.
@tizuby
Just make sure you have updated to 2.0.0.7, and you should be good for the duration of RW1.1. Ship the dll with your mod as usual, unless you have a HugsLib dependency, then there is no need. I can't recommend depending on the Harmony workshop item as of RW1.1, since we don't know if it will be updated to newer versions- if it does, we have a mess of incompatibility again.
I had 2.0.0.7 packaged with it originally and was still getting the crashes (same UI null ref as others). Been trying various tweaks all night to no effect.
Wonder if something else is going on on-top of the inconsistency issue.
Can take a peak at https://github.com/tizubythefizo/RoadsOfTheRim/releases as that's the version with harmony 2.0.0.7 packaged that's having issues.
Part of the issue was HugsLib reverting to 6.2.1 (with Harmony 2.0.0.6) as I was identifying the cause of the conflicts. With 2.0.0.6 being the first Harmony dll in the load order, it was preventing mods built against 2.0.0.7 from working properly.
I just tested again and am still getting the UIRoot null ref when trying to build. I reverted back to before I changed it to depend on the WS version of Harmony and verified that it's using 2.0.0.7 (I edited my earlier post to include the github link, in case you want to see if it repros on your end).
As I rebuild my mods to the latest version of HugsLib, I noticed that there is this message in my Visual Studio:
Quote:
The primary reference "0Harmony" could not be resolved because it was built against the ".NETFramework,Version=v4.7.2" framework. This is a higher version than the currently targeted framework ".NETFramework,Version=v4.0".
End of quote.
I am referencing the latest HugsLib library (as of writing) and v2.0.0.7 Harmony library. My project is using NET Framework v4.0.
It may be that the wrong version of Harmony library got included...?
Edit: My dumbass did not load HugsLib before my mod... issue is fixed by placing HugsLib in the loading list after Core.