Omgski
Greenhorn
Good day fellow farmers,
My game has always run stable and never crashed until today.
When going to bed and loading the next day the screen stays black and an error gets spammed in the SMAPI console (see below).
It seems to involve a child, maybe growing up crashes the game?
The other thing I can think off is that the child of the other player is not located in the crib and instead floats off-screen at the adventurers guild (very weird glitch).
This player now tried for a second child, maybe that crashes the game?
Is there anyone that has an idea on how to fix this? :(
I am running SMAPI 3.14.6 with Stardew Valley 1.5.6 on Windows 10.
Update: I have ran the error log through the parser for better readability,
https://smapi.io/log/d16d11b9ac44477593ebe3e1172f5a09
Fixed: I have managed to fix the problem myself. Though I should report the fix for people with the same problem. The child was located in a strange location called 'Custom_child-name_WarpRoom' (replace child-name with the name of your child). By warping the child back to the right cabin and resetting the location they returned to their crib and this fixed the problem. In my case the commands 'debug warp child-name cabin' & 'debug r' fixed the problem.
My game has always run stable and never crashed until today.
When going to bed and loading the next day the screen stays black and an error gets spammed in the SMAPI console (see below).
It seems to involve a child, maybe growing up crashes the game?
The other thing I can think off is that the child of the other player is not located in the crib and instead floats off-screen at the adventurers guild (very weird glitch).
This player now tried for a second child, maybe that crashes the game?
Is there anyone that has an idea on how to fix this? :(
I am running SMAPI 3.14.6 with Stardew Valley 1.5.6 on Windows 10.
Update: I have ran the error log through the parser for better readability,
https://smapi.io/log/d16d11b9ac44477593ebe3e1172f5a09
Fixed: I have managed to fix the problem myself. Though I should report the fix for people with the same problem. The child was located in a strange location called 'Custom_child-name_WarpRoom' (replace child-name with the name of your child). By warping the child back to the right cabin and resetting the location they returned to their crib and this fixed the problem. In my case the commands 'debug warp child-name cabin' & 'debug r' fixed the problem.
Last edited: