Install Steam
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)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
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
Thank you for taking the time to respond.
There was also an Incident-type error...
This is completely my adjustment error. I apologize for displaying it in the log.
Thank you for all your very nice mods.
Thank you again and again for your support.
I looked into it, found the issue and uploaded a fix. I had a patch specifically for Dubs Rimkit but it was already being caught by an earlier patch. As a result it was patched twice causing errors.
In your log you also have another error which is probably related to my More Quests tweak. All your storytellers are giving the error "minSpacingDays too high compared to max number of incidents". Basically you've set the minSpacingDays too high for the amount of incidents you've set. For instance you can't expect 15 incidents to occur within 7 days if they require minimum of 1 day between them.
Sorry for the inconvenience.
Nice to meet you. I am a person who has been using your useful mod.
I am contacting you because I have found a conflict between mods.
I am sorry to bother you, but I would appreciate it if you could check it out.
Using DubsRimkit and [FSF] FrozenSnowFox Tweaks
with a red error
<apparel><countsAsClothingForNudity>false</countsAsClothingForNudity><wearPerDay>0</wearPerDay>
from I found an error that starts with
Detailed log
https://gist.github.com/HugsLibRecordKeeper/167b88cc19b2062fd1ba3d656eb5261a
Thank you for your time and we would appreciate it if you could check it out.
Also, I am not an English speaker, so I apologize if I did not communicate well.
I'm not sure how or why this happens. However I do know steam can be a bit weird with downloading updates at times. Some people have gotten stuck with mod files that are months out of date. Then there's instances such as yours where for whatever reason it didn't download all the files. Verifying the game files at times like this can usually fix things.
How would my game files become corrupted like that?
I grabbed a copy from steam to check the files and it looks fine. I also didn't mess with Pasture Grass. Try unsubscribing and resubscribing and if that doesn't work try verifying your game files. I get the feeling steam messed something up when it updated your mod files.
SaveableFromNode exception: System.NullReferenceException: Object reference not set to an instance of an object
[Ref 5C1299F0] Duplicate stacktrace, see ref for original
Subnode:
<thing Class="Plant"><def>FSFPastureGrass</def><id>FSFPastureGrass2515994</id><map>0</map><pos>(171, 0, 216)</pos><health>85</health><questTags IsNull="True" /><spawnedTick>10589834</spawnedTick><growth>1</growth><age>1764000</age><unlitTicks>24000</unlitTicks><sown>True</sown></thing>
UnityEngine.StackTraceUtility:ExtractStackTrace ()
(wrapper dynamic-method) MonoMod.Utils.DynamicMethodDefinition:Verse.Log.Error_Patch5 (string)
I also had a grow zone around it, so that they would automatically plant it back when it dies, and I also updated the Smart Farming mod, so it might be related to that as well.
It has a lifespan of one year. It might have died of old age? In fact it might not be a bad idea to change that so it straight up doesn't die.