Each time I launch the game I get a black screen and this window pop up.
Assertion Failed new_node.name() == “mixins” II new_node.type() - - mixin_node.type()(C:\rb\home\root\SH-OB0-Build\stonehearth\source\resources\res_manager.cpp:657)
There is a mod causing the error because once I moved all the extra mods the game launched fine. Will test to see if I can figure out which one it is.
So far there seems to be an issue with both the cookmod @Froggy and the brewerymod @Wiese2007
I wonder if it is because they added watermelons to the RC Kingdom?
EDIT
So far the only three mods that seem to be causing this issue are:
cookmod (Corrected on July 1st good to go now)
brewerymod (Corrected on July 1st good to go now)
settlementdecor (Corrected on July 3rd good to go now)
the following mods do not cause this issue
anorien_biome
better_stockpiles
clocks
dark_knight
debugtools
endpieces
furniture_expansion_plus
grove_biome
jomaxro_doorway_mod
LocksOfColour
lodewall-boxes
lodewall-lights
market_stalls
paladin
runes
Spiros_container_mod
Spiros_window_mod
terrain_colors
tuhalu
I tested one by one to see which were causing the Assertion error.
It was the settlement decor mod for me
@8BitCrab how do I change the topic name or can you do that for me. This should be Mods that need updating for build 566. As this error is external to the core content and the current title does not reflect this.
i can confirm that there is something with the cookmod, brewerymod and settlementdecor mod … i think it could be the observer but like i know there is no observer in the brewerymod ^^
Assertion Failed: new_node.name() == “mixins” || new_node.type() == mixin_node.type()(C:\rb\ihome\root\SH-OB0-BUILD\stonehearth\source\resources\res_manager.cpp:657)
thats the errormessage
edit: looks like it has something with the initial_crops todo
Thanks for the heads up. I’ll take a look now 
if you find it - please inform me ^^ i have found only that it has something todo with the crops (also change them to the new style doesnt work) ^^
Fixing the initial crops worked for me. Check for typos 
Plus any dependencies from my mod, which hasn’t been updated yet might cause yours to explode
@Geokhan Thanks! You can now strike me from the list of offending modders!!
i test it without your mod at the moment 
edit: ok i have found it - was really an old typoissue xD ^^
edited the list to show cookmod was good to go.
then strike me now too xD
I have struck Brewerymod as well.
One of the bad things about having so many mods is that it is hard to go back to vanilla. It like an coffee addiction, I just cant function without them LOL.
Looks like all the mods have been updated
@8BitCrab could you lock this thread, it is no longer needed
